From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2] config: disable RTE_NEXT_ABI by default Date: Thu, 4 Oct 2018 16:28:27 +0100 Message-ID: <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com> References: <20181004154306.65867-1-ferruh.yigit@intel.com> <20181004154829.66523-1-ferruh.yigit@intel.com> <1785611.eL8Z1dKoq2@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, Neil Horman , Luca Boccassi , Christian Ehrhardt To: Thomas Monjalon Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 649171B518 for ; Thu, 4 Oct 2018 17:28:33 +0200 (CEST) In-Reply-To: <1785611.eL8Z1dKoq2@xps> Content-Language: en-US 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 10/4/2018 4:10 PM, Thomas Monjalon wrote: > 04/10/2018 17:48, Ferruh Yigit: >> Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for >> the current release and these APIs are targeted for further release. > > It seems nobody is using it in last releases. > >> RTE_NEXT_ABI shouldn't be enabled by default. > > The reason for having it enabled by default is that when you build DPDK > yourself, you probably want the latest features. > If packaged properly for stability, it is easy to disable it in > the package recipe. My concern was (if this has been used), user may get unstable APIs and without explicitly being aware of it.