From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, probb@iol.unh.edu
Subject: Re: [RFC PATCH] build: automatically report minimum meson version
Date: Wed, 9 Oct 2024 09:40:17 -0700 [thread overview]
Message-ID: <20241009094017.0852ec51@hermes.local> (raw)
In-Reply-To: <20241009152417.4028297-1-bruce.richardson@intel.com>
On Wed, 9 Oct 2024 16:24:01 +0100
Bruce Richardson <bruce.richardson@intel.com> wrote:
> Add a script to buildtools to report the minimum meson version given in
> our meson.build file. Then use this script in two ways:
>
> 1. in the .ci/linux-setup.sh script, use the auto-determined minimum
> version to set up the CI, rather than hard-coding it.
> 2. in meson.build call the script to report the version. This serves as
> a sanity check to ensure that any changes to meson.build file do not
> break the script.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Make sense, kind of annoying that it requires so many lines to do this
but very understandable.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2024-10-09 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 15:24 [RFC PATCH] build: automatically report minimum meson version Bruce Richardson
2024-10-09 16:40 ` Stephen Hemminger [this message]
2024-10-14 16:31 ` Patrick Robb
2025-05-13 8:59 ` [PATCH v2] " Bruce Richardson
2025-05-15 7:09 ` David Marchand
2025-05-15 9:36 ` Bruce Richardson
2025-05-15 11:39 ` David Marchand
2025-05-15 12:28 ` Patrick Robb
2025-05-15 12:54 ` Bruce Richardson
2025-05-15 13:46 ` [PATCH v3] " Bruce Richardson
2025-05-16 7:33 ` David Marchand
2025-05-16 11:28 ` zhoumin
2025-05-16 11:32 ` zhoumin
2025-06-09 9:44 ` Thomas Monjalon
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=20241009094017.0852ec51@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=probb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.