DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: dev <dev@dpdk.org>
Subject: Re: Meson Versions for DPDK
Date: Mon, 12 Sep 2022 18:11:15 +0100	[thread overview]
Message-ID: <Yx9oM5VXenJPKOIv@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <YwzrHnXRP9kzhm7F@bricha3-MOBL.ger.corp.intel.com>

On Mon, Aug 29, 2022 at 05:36:46PM +0100, Bruce Richardson wrote:
> On Mon, Aug 29, 2022 at 08:59:04AM -0400, Lincoln Lavoie wrote:
> >    Hi All,
> >    The current version of meson is pinned to 0.49.2, which was released in
> >    February 2019.  At least it's pinned to that version within
> >    .ci/linux-setup.sh.
> >    Current version of 0.63.1, and defaults "shipped" with operating
> >    systems are newer than the 0.49.2 version and do break the DPDK
> >    compile.
> >    It's not practical to always support the newest (i.e. removing any
> >    pinning of the version), but it also shouldn't be something we pin to a
> >    single version forever.  So, opening up a discussion about what
> >    strategy could be used for maintaining the meson version that is
> >    "supported" for dpdk.  That version would be used for all CI testing.
> >    Cheers,
> >    Lincoln
> >    --
> 
> To get the discussion started, I think we need to look at what the default
> versions shipped with common distributions are. Thankfully, we are not
> limited to those defaults, due to the ease of installing updated versions
> using pip3, but it helps to serve as a baseline. I see Ubuntu 20.04 lists
> 0.53.2 as the baseline version there [1], for example. That may be a good
> minimum to look at, though we perhaps want to update beyond that.
> 
> /Bruce
> 
> [1] https://packages.ubuntu.com/focal/devel/meson

In the absense of any objections or further discussion here, I've posted a
patch to bump meson minimum version to 0.53. Ref:
http://patches.dpdk.org/project/dpdk/patch/20220912170747.3128065-2-bruce.richardson@intel.com/

      reply	other threads:[~2022-09-12 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 12:59 Lincoln Lavoie
2022-08-29 16:36 ` Bruce Richardson
2022-09-12 17:11   ` Bruce Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yx9oM5VXenJPKOIv@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).