From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 28CEAA04C0; Fri, 25 Sep 2020 11:23:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 88F2A1E54A; Fri, 25 Sep 2020 11:23:05 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 955B11D14B; Fri, 25 Sep 2020 11:23:03 +0200 (CEST) IronPort-SDR: xtK3oGOygQ9q/5KOCX1xVaJgYS6D+q+6Ik+TK/BbwrVy4Xw503Eo9VNbE2D9isoDAhzKOZGf+U scpa8gq6WM4A== X-IronPort-AV: E=McAfee;i="6000,8403,9754"; a="158831887" X-IronPort-AV: E=Sophos;i="5.77,301,1596524400"; d="scan'208";a="158831887" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Sep 2020 02:23:02 -0700 IronPort-SDR: NbYO9C79RDD+hGidlLOcuXCEIMsYzYJgC8g+iI8yz/Mtecc8StCYIjdKHLJ/pgbxDGfboeWGge ipHB441IPLxg== X-IronPort-AV: E=Sophos;i="5.77,301,1596524400"; d="scan'208";a="487396248" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.51.38]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 25 Sep 2020 02:23:00 -0700 Date: Fri, 25 Sep 2020 10:22:57 +0100 From: Bruce Richardson To: Dmitry Kozlyuk Cc: Morten =?iso-8859-1?Q?Br=F8rup?= , John Alexander , dev@dpdk.org, techboard@dpdk.org Message-ID: <20200925092257.GC923@bricha3-MOBL.ger.corp.intel.com> References: <20200924154308.GF382@bricha3-MOBL.ger.corp.intel.com> <98CBD80474FA8B44BF855DF32C47DC35C61326@smartserver.smartshare.dk> <20200925084122.GA923@bricha3-MOBL.ger.corp.intel.com> <20200925121933.517c645c@sovereign> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200925121933.517c645c@sovereign> Subject: Re: [dpdk-dev] Meson Minimum Version 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Sep 25, 2020 at 12:19:33PM +0300, Dmitry Kozlyuk wrote: > On Fri, 25 Sep 2020 09:41:22 +0100, Bruce Richardson wrote: > > On Fri, Sep 25, 2020 at 09:31:53AM +0200, Morten Brørup wrote: > > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson > [snip] > > > In short, my primary concern is: What could realistically go wrong if the required version of Meson is buggy? > > > > > > Bruce, you have worked for quite a while with Meson/Ninja by now, so perhaps you can assess this risk based on your experience. > > > > > I'd say the risk in this case is small, especially since I see that 0.56 of > > meson is well under way for development and may well be released before > > DPDK 20.11. Generally backwards compatibilty of meson is excellent as they > > have comprehensive test suite for all features. > > > > Rather than any bugginess, my concern was purely requiring people to update > > meson using "pip3", but I suppose that's not really a big deal, and when > > using pip update it defaults to just updating the copy for the local user, > > not system-wide. > > Speaking for Windows, at least twice this year there were incompatibilities > between _minor_ versions of Meson, due to admitted bugs in Meson. However, > IMO this is an argument for using just _exact_ version, not necessarily an old > one. Pip facilitates this better than OS package manager, because developer > controls the version and can easily switch, regardless of distro updates. > Thus, John's upgrade suggestion and transition to pip both look reasonable. > Seems that meson must be a bit more fragile on windows then, which is a pity (and perhaps their regression tests aren't as good as I thought). On Linux, since version 0.40 I think only one version, 0.47.0, caused an issue for us, which was fixed in 0.47.1. However, having a recommended version to use can work too.