From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 3247A532D for ; Mon, 18 Sep 2017 13:09:42 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Sep 2017 04:09:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,412,1500966000"; d="scan'208";a="901297340" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.24]) by FMSMGA003.fm.intel.com with SMTP; 18 Sep 2017 04:09:40 -0700 Received: by (sSMTP sendmail emulation); Mon, 18 Sep 2017 12:09:39 +0100 Date: Mon, 18 Sep 2017 12:09:39 +0100 From: Bruce Richardson To: luca.boccassi@gmail.com Cc: dev@dpdk.org, Luca Boccassi Message-ID: <20170918110938.GA10264@bricha3-MOBL3.ger.corp.intel.com> References: <20170915173612.13636-1-luca.boccassi@gmail.com> <20170915173612.13636-2-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170915173612.13636-2-luca.boccassi@gmail.com> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.8.3 (2017-05-23) Subject: Re: [dpdk-dev] [PATCH 1/3] build: rename pkgconfig to libdpdk.pc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 11:09:43 -0000 On Fri, Sep 15, 2017 at 06:36:10PM +0100, luca.boccassi@gmail.com wrote: > From: Luca Boccassi > > In Debian and Ubuntu we have been shipping a pkgconfig file for DPDK > for more than a year now, and the filename is libdpdk.pc. > A few downstream projects, like OVS and Collectd, have adopted the > use of libdpdk.pc in their build systems as well. > In order to maintain backward compatibility, rename the file from > DPDK.pc to libdpdk.pc. > > Signed-off-by: Luca Boccassi > --- I find the 'lib' bit strange, but if that is what is already out there, then we should keep it for compatibility. In future, we might create two pkgconfig files to transition over to a new name, but to start with lets use what is being looked for by our dependencies. Acked-by: Bruce Richardson