From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [RFC PATCH 0/6] change legacy linuxapp/bsdapp names
Date: Wed, 13 Mar 2019 14:59:08 +0100
Message-ID: <2347388.E9kf87BXsl@xps>
References: <20190306162242.65375-1-bruce.richardson@intel.com>
 <19421689.NtES9yoMkj@xps> <af1c590b-fed6-be0e-c8c7-b2169fee3d18@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com
 [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 4A181239
 for <dev@dpdk.org>; Wed, 13 Mar 2019 14:59:12 +0100 (CET)
In-Reply-To: <af1c590b-fed6-be0e-c8c7-b2169fee3d18@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

13/03/2019 14:41, Ferruh Yigit:
> On 3/12/2019 10:13 PM, Thomas Monjalon wrote:
> >> Bruce Richardson (6):
> >>   eal/bsdapp: rename to freebsd
> >>   eal/linuxapp: rename to linux
> >>   build/linux: rename macro from LINUXAPP to LINUX
> >>   build/freebsd: rename macro from BSDPAPP to FREEBSD
> >>   build/meson: change linuxapp to linux in meson cross files
> >>   build: allow linux and freebsd in build configs
> > 
> > Applied, thanks
> 
> This has potential to break some automation/scripts since changes the names of
> the config files:
> 'make T=x86_64-native-linuxapp-gcc config' becomes
> 'make T=x86_64-native-linux-gcc config' etc...
> 
> I suggest highlighting this change in release notes!

No, the old names should still work.
Otherwise, it would be an API breakage, which is very bad!