From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Young <dave@youngcopy.com>, <dev@dpdk.org>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH v2] docs: freebsd: Update to 20.11
Date: Mon, 17 Jul 2023 14:35:07 +0100 [thread overview]
Message-ID: <ZLVDi4rJJCaUjMOI@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <9128157.CDJkKcVGEf@thomas>
On Mon, Jul 03, 2023 at 05:19:18PM +0200, Thomas Monjalon wrote:
> 30/06/2023 18:41, David Young:
> > This patch updates the installation instructions for DPDK on FreeBSD.
> > It specifies the explicit version of DPDK (20.11) to be installed.
> > This change is important as the 'dpdk' package is an alias and doesn't
> > always point to the latest version. By specifying the explicit version,
> > we make it clear which version is to be installed. The page previously
> > showed 'pkg install dpdk' without specifying the version.
>
> I understand it can be helpful to choose a specific version.
> But dpdk20.11 is not necessarily the latest one,
> and it could be useful to show both approaches in the doc.
>
The FreeBSD ports don't always track the latest DPDK LTS sadly. Originally
I used to just update the existing "dpdk" port to the latest version each
release, but with the API policy and LTS compatibility guarantees, we now
need separate per-LTS DPDK packages. The old "dpdk" package is 19.11 and I
have a patch submitted to mark it as deprecated and add a new "dpdk22.11"
package instead to replace it [never did do 21.11 - two ports to manage is
easier for me that 3!]. The patch is undergoing review from the ports team,
and I have still to rework based on the feedback.
Therefore, I think the docs should just cover using "pkg search" to find
DPDK port packages, and recommending selecting the latest one.
/Bruce
next prev parent reply other threads:[~2023-07-17 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 18:12 [PATCH] Updated to dpdk20.11 David Young
2023-06-29 18:26 ` Aaron Conole
2023-06-30 16:41 ` [PATCH v2] docs: freebsd: Update to 20.11 David Young
2023-07-03 15:19 ` Thomas Monjalon
2023-07-17 13:35 ` Bruce Richardson [this message]
2023-07-06 20:36 ` [PATCH v3] " David Young
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=ZLVDi4rJJCaUjMOI@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=dave@youngcopy.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).