DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] doc: update FreeBSD python version
Date: Mon, 3 Nov 2025 19:57:37 +0000	[thread overview]
Message-ID: <aQkJMHX6NWmZcJEd@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251103193038.135022-1-stephen@networkplumber.org>

On Mon, Nov 03, 2025 at 11:30:38AM -0800, Stephen Hemminger wrote:
> The version python used in current FreeBSD stable release 14.3
> is now 3.11. Update documentation accordingly.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  doc/guides/freebsd_gsg/build_dpdk.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/doc/guides/freebsd_gsg/build_dpdk.rst b/doc/guides/freebsd_gsg/build_dpdk.rst
> index f98292bf41..c8b2964a4b 100644
> --- a/doc/guides/freebsd_gsg/build_dpdk.rst
> +++ b/doc/guides/freebsd_gsg/build_dpdk.rst
> @@ -16,16 +16,16 @@ The following FreeBSD packages are required to build DPDK:
>  * meson
>  * ninja
>  * pkgconf
> -* py38-pyelftools
> +* py311-pyelftools
>  
>  .. note:
>  
>    The specific package for pyelftools is dependent on the version of python in use,
> -  Python 3.8 being the version at type of writing, hence the ``py38`` prefix.
> +  Python 3.11 being the version at type of writing, hence the ``py311`` prefix.
>  
>  These can be installed using (as root)::
>  
> -  pkg install meson pkgconf py38-pyelftools
> +  pkg install meson pkgconf py311-pyelftools
>  
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

I always find the python version included in the packages annoying, but I
don't think there is anything we can do about this. Thanks for the update.


      reply	other threads:[~2025-11-03 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 19:30 Stephen Hemminger
2025-11-03 19: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=aQkJMHX6NWmZcJEd@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).