From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] config: disable RTE_NEXT_ABI by default Date: Thu, 04 Oct 2018 17:10:09 +0200 Message-ID: <1785611.eL8Z1dKoq2@xps> References: <20181004154306.65867-1-ferruh.yigit@intel.com> <20181004154829.66523-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Neil Horman , Luca Boccassi , Christian Ehrhardt To: Ferruh Yigit Return-path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 0F11F1B4FC for ; Thu, 4 Oct 2018 17:10:13 +0200 (CEST) In-Reply-To: <20181004154829.66523-1-ferruh.yigit@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" 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.