DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Robin Jarry <rjarry@redhat.com>
Cc: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2 0/4] simplify doing 32-bit DPDK builds
Date: Thu, 19 Sep 2024 13:57:21 +0100	[thread overview]
Message-ID: <ZuwfsT6iRqcjnxRe@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <D4A8ZTYV7YH8.3DOPF45BVGVGG@redhat.com>

On Thu, Sep 19, 2024 at 02:09:20PM +0200, Robin Jarry wrote:
> 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.
> 
Looking down that list at the link, I would agree that 3.9 is a good
minimum. That covers us for all the distros we care about, I think.

/Bruce

      reply	other threads:[~2024-09-19 12:57 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
2024-09-19 12:57               ` 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=ZuwfsT6iRqcjnxRe@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=rjarry@redhat.com \
    /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).