From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Boccassi Subject: Re: Change in binary name w/ meson build Date: Wed, 12 Sep 2018 10:34:42 +0100 Message-ID: <1536744882.10952.38.camel@debian.org> References: <20180907141342.GA21576@bricha3-MOBL.ger.corp.intel.com> <20180907152418.GA14360@bricha3-MOBL.ger.corp.intel.com> <20180912093021.GA15632@bricha3-MOBL.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: Marcelo Ricardo Leitner , Thomas Monjalon , "dev@dpdk.org" , christian.ehrhardt@canonical.com To: Bruce Richardson , Shahaf Shuler Return-path: Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68]) by dpdk.org (Postfix) with ESMTP id 8A63C1559 for ; Wed, 12 Sep 2018 11:34:46 +0200 (CEST) Received: by mail-wm0-f68.google.com with SMTP id j192-v6so1609290wmj.1 for ; Wed, 12 Sep 2018 02:34:46 -0700 (PDT) In-Reply-To: <20180912093021.GA15632@bricha3-MOBL.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 2018-09-12 at 10:30 +0100, Bruce Richardson wrote: > On Wed, Sep 12, 2018 at 06:21:06AM +0000, Shahaf Shuler wrote: > > Friday, September 7, 2018 6:24 PM, Bruce Richardson: > > > Subject: Re: [dpdk-dev] Change in binary name w/ meson build > > >=20 > > > On Fri, Sep 07, 2018 at 03:13:43PM +0100, Bruce Richardson wrote: > > > > On Wed, Sep 05, 2018 at 11:52:10AM +0000, Shahaf Shuler wrote: > > > > > =C2=A0=C2=A0=C2=A0Hi Bruce, > > > > >=20 > > > > >=20 > > > > > =C2=A0=C2=A0=C2=A0Playing w/ meson build I got to know that the b= inary name > > > > > for testpmd > > > > > =C2=A0=C2=A0=C2=A0got changed to dpdk-testpmd. > > > > >=20 > > > > >=20 > > > > > =C2=A0=C2=A0=C2=A0Not sure if it was discussed or not before, but= such > > > > > change will affect > > > > > =C2=A0=C2=A0=C2=A0all the automation used to run testpmd w/ the o= ld build > > > > > system. > > > > >=20 > > > > >=20 > > > > > =C2=A0=C2=A0=C2=A0What is the reason for the change in the name? > > > >=20 > > > > The primary driver was that the autotest binary could not be > > > > called "test" > > > > any more, since that is a reserved name. When appending a dpdk > > > > prefix > > > > to the test binary, I felt for consistency that other binaries > > > > should > > > > have a dpdk prefix too, to indicate that they come from DPDK. > > > > If this > > > > is a problem, we can remove the prefix from the binaries easily > > > > enough. > > > >=20 > > >=20 > > > Also to point out that when building with meson the scripting is > > > going to have > > > to change anyway, right. The actual build commands are different, > > > the > > > configuration commands are different, and the directories the > > > resulting > > > binaries are placed in are different too. Therefore, I'd like to > > > keep the name > > > prefixes if possible, since for automated tooling on DPDK there > > > are going to > > > have to be lots of other changes anyway. > > >=20 > > > For packagers, the rename I understand could be problematic, but > > > that could > > > probably be solved by symlinks in the install phase. > >=20 > > I am fine w/ the testpmd -> dpdk-testpmd change as it is more > > correct to put it explicitly under the dpdk namespace. > > I was raising this point because I am not sure it was explicitly > > mentioned on the release notes and was hoping to get feedback also > > from the people who build dpdk for distro > >=20 >=20 > Agreed, I should have got wider feedback for this change at the time, > but > it's not to late to fix if it is problematic, I think. I too like > having > the namespacing, though. >=20 > /Bruce I can ship backward-compatibility symlinks easily for binary programs in Debian/Ubuntu (unlike for libraries where it's a bit more difficult), so personally I'm OK with namespacing things. Christian? --=20 Kind regards, Luca Boccassi