From: "Robin Jarry" <rjarry@redhat.com>
To: "David Marchand" <david.marchand@redhat.com>,
"Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 0/4] simplify doing 32-bit DPDK builds
Date: Thu, 19 Sep 2024 14:09:20 +0200 [thread overview]
Message-ID: <D4A8ZTYV7YH8.3DOPF45BVGVGG@redhat.com> (raw)
In-Reply-To: <CAJFAV8wmAhRhqODkRpGCD_qpVupyzLQ_oMGg7OuE_4ogMSWReQ@mail.gmail.com>
David Marchand, Sep 19, 2024 at 13:32:
> On Thu, Sep 19, 2024 at 1:15 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Thu, Sep 19, 2024 at 10:08:21AM +0200, David Marchand wrote:
> > > On Thu, Sep 19, 2024 at 10:02 AM Bruce Richardson
> > > <bruce.richardson@intel.com> wrote:
> > > > Overall, I think we haven't increased our minimum meson version in some
> > > > time. Maybe it's time to consider doing so in this release or the next one?
> > > > Need to look through release notes to see how far forward to jump to see
> > > > what extra features might be useful for us to leverage.
> > >
> > > That's an option, just be careful that there is some tie with python
> > > versions iirc.
> > >
> > Right. Do we have a minimum python version from various distros that we
> > need to support?
>
> We have a minimum version (3.6) in DPDK, harder to tell with all the
> distros around.
> Robin, any idea/guidance?
3.6 is really old. I think it is safe to bump it to at least 3.9.
https://repology.org/project/python/badges
It depends how backwards compatible DPDK wants to remain.
next prev parent reply other threads:[~2024-09-19 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 13:57 [PATCH] config: add 32-bit cross-compilation x86 target Bruce Richardson
2024-09-06 15:34 ` Medvedkin, Vladimir
2024-09-06 16:12 ` [PATCH v2 0/4] simplify doing 32-bit DPDK builds Bruce Richardson
2024-09-06 16:12 ` [PATCH v2 1/4] config: add 32-bit x86 debian cross-compilation file Bruce Richardson
2024-09-06 16:12 ` [PATCH v2 2/4] config: add fedora 32-bit x86 cross-compile file Bruce Richardson
2024-09-06 16:12 ` [PATCH v2 3/4] config: add arch 32-bit cross-compilation file Bruce Richardson
2024-09-06 16:12 ` [PATCH v2 4/4] devtools/test-meson-builds: use cross files for 32bit build Bruce Richardson
2024-09-19 7:44 ` [PATCH v2 0/4] simplify doing 32-bit DPDK builds David Marchand
2024-09-19 7:52 ` Bruce Richardson
2024-09-19 8:02 ` Bruce Richardson
2024-09-19 8:08 ` David Marchand
2024-09-19 11:15 ` Bruce Richardson
2024-09-19 11:32 ` David Marchand
2024-09-19 12:09 ` Robin Jarry [this message]
2024-09-19 12:57 ` 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=D4A8ZTYV7YH8.3DOPF45BVGVGG@redhat.com \
--to=rjarry@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--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).