From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: dev <dev@dpdk.org>
Subject: Meson Versions for DPDK
Date: Mon, 29 Aug 2022 08:59:04 -0400 [thread overview]
Message-ID: <CAOE1vsNoDP0oOLkj2J4LRttXxTL7F4w1sd=KHGOWSvu+onZGFw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
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
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2090 bytes --]
next reply other threads:[~2022-08-29 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 12:59 Lincoln Lavoie [this message]
2022-08-29 16:36 ` Bruce Richardson
2022-09-12 17:11 ` Bruce Richardson
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='CAOE1vsNoDP0oOLkj2J4LRttXxTL7F4w1sd=KHGOWSvu+onZGFw@mail.gmail.com' \
--to=lylavoie@iol.unh.edu \
--cc=dev@dpdk.org \
/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).