From: Luca Boccassi <bluca@debian.org>
To: Ray Kinsella <mdr@ashroe.eu>,
Bruce Richardson <bruce.richardson@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-techboard] DPDK ABI/API Stability
Date: Thu, 04 Apr 2019 14:21:19 +0100 [thread overview]
Message-ID: <60afc83fc723050914d617461607a9c5a72d3017.camel@debian.org> (raw)
Message-ID: <20190404132119.YS8sGf9gua6fdxHFS-U9H5pjoRhZAQrOdqSV-1sM18U@z> (raw)
In-Reply-To: <3055e4ce-767b-ab43-43ac-c3604fd3ea5c@ashroe.eu>
On Thu, 2019-04-04 at 14:05 +0100, Ray Kinsella wrote:
> > > Question for Kevin, Luca and others who look at distro-packaging:
> > > is
> > > it the
> > > case that each distro will only ship one version of DPDK, or is
> > > it
> > > possible
> > > that if we have ABI breaks, a distro will provide two copies of
> > > DPDK
> > > simultaneously, e.g. a 19.11 ABI version and a 20.11 ABI version?
> >
> > We can ship multiple versions, although it's more work so there
> > should
> > be a good reason to do it.
>
> Well you already kind of do right.
> You ship 16.11.8 with Debian 9 and then 18.11 with Debian 9
> backports.
Yes indeed - backports has a different policy and is not part of
"Debian main" - for example, stability and security support are not
guaranteed. Also there is no guarantee of compatibility of co-
installability - while you can have the individual libraries from each
version at the same time, you can't have both libdpdk-dev packages
which are necessary to build an application. So you have to choose and
install either libdpdk-dev=16.11 or libdpdk-dev=18.11.
It is possible to have multiple versions in the same archive at the
same time, and with multiple -dev packages, and that's what I meant
when I mentioned it was more work.
> > At the moment in Debian and Ubuntu we don't,
> > and we tend to ship whatever the latest LTS version is at the
> > distro
> > freeze milestone - for example Debian 10 which will be released
> > soon
> > (TM) will have 18.11.0.
>
> Presumably when 19.11 arrives, it will land in Debian 10 backports
> similarly.
>
> I assume anything that lands in backports is not guaranteed to be ABI
> compatible with stable?
Yes, there's no guarantee.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-04-04 13:21 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:42 [dpdk-dev] " Ray Kinsella
2019-04-03 15:42 ` Ray Kinsella
2019-04-03 19:53 ` Luca Boccassi
2019-04-03 19:53 ` Luca Boccassi
2019-04-04 9:29 ` Burakov, Anatoly
2019-04-04 9:29 ` Burakov, Anatoly
2019-04-04 10:54 ` [dpdk-dev] [dpdk-techboard] " Bruce Richardson
2019-04-04 10:54 ` Bruce Richardson
2019-04-04 12:02 ` Luca Boccassi
2019-04-04 12:02 ` Luca Boccassi
2019-04-04 13:05 ` Ray Kinsella
2019-04-04 13:05 ` Ray Kinsella
2019-04-04 13:10 ` Bruce Richardson
2019-04-04 13:10 ` Bruce Richardson
2019-04-05 13:25 ` Ray Kinsella
2019-04-05 13:25 ` Ray Kinsella
2019-04-07 9:37 ` Thomas Monjalon
2019-04-07 9:37 ` Thomas Monjalon
2019-04-04 13:21 ` Luca Boccassi [this message]
2019-04-04 13:21 ` Luca Boccassi
2019-04-04 12:52 ` Ray Kinsella
2019-04-04 12:52 ` Ray Kinsella
2019-04-04 14:07 ` Burakov, Anatoly
2019-04-04 14:07 ` Burakov, Anatoly
2019-04-07 9:48 ` Thomas Monjalon
2019-04-07 9:48 ` Thomas Monjalon
2019-04-08 9:04 ` Ray Kinsella
2019-04-08 9:04 ` Ray Kinsella
2019-04-08 10:15 ` Burakov, Anatoly
2019-04-08 10:15 ` Burakov, Anatoly
2019-04-08 13:00 ` Ray Kinsella
2019-04-08 13:00 ` Ray Kinsella
2019-04-08 13:38 ` Burakov, Anatoly
2019-04-08 13:38 ` Burakov, Anatoly
2019-04-08 13:58 ` David Marchand
2019-04-08 13:58 ` David Marchand
2019-04-08 14:02 ` Burakov, Anatoly
2019-04-08 14:02 ` Burakov, Anatoly
2019-04-08 14:38 ` David Marchand
2019-04-08 14:38 ` David Marchand
2019-04-08 15:13 ` Stephen Hemminger
2019-04-08 15:13 ` Stephen Hemminger
2019-04-08 15:49 ` Burakov, Anatoly
2019-04-08 15:49 ` Burakov, Anatoly
2019-04-10 8:35 ` David Marchand
2019-04-10 8:35 ` David Marchand
2019-04-08 15:50 ` Burakov, Anatoly
2019-04-08 15:50 ` Burakov, Anatoly
2019-04-09 9:42 ` Ray Kinsella
2019-04-09 9:42 ` Ray Kinsella
2019-04-14 0:42 ` Neil Horman
2019-04-14 0:42 ` Neil Horman
2019-04-15 9:10 ` Bruce Richardson
2019-04-15 9:10 ` Bruce Richardson
2019-04-04 15:51 ` Stephen Hemminger
2019-04-04 15:51 ` Stephen Hemminger
2019-04-04 16:37 ` Burakov, Anatoly
2019-04-04 16:37 ` Burakov, Anatoly
2019-04-04 16:56 ` Kevin Traynor
2019-04-04 16:56 ` Kevin Traynor
2019-04-04 19:08 ` Wiles, Keith
2019-04-04 19:08 ` Wiles, Keith
2019-04-04 20:13 ` Kevin Traynor
2019-04-04 20:13 ` Kevin Traynor
2019-04-05 13:30 ` Ray Kinsella
2019-04-05 13:30 ` Ray Kinsella
2019-04-05 13:29 ` Ray Kinsella
2019-04-05 13:29 ` Ray Kinsella
2019-04-04 9:47 ` [dpdk-dev] " Kevin Traynor
2019-04-04 9:47 ` Kevin Traynor
2019-04-04 13:16 ` Ray Kinsella
2019-04-04 13:16 ` Ray Kinsella
2019-04-10 5:14 ` Honnappa Nagarahalli
2019-04-10 5:14 ` Honnappa Nagarahalli
2019-04-10 9:03 ` [dpdk-dev] [dpdk-techboard] " Bruce Richardson
2019-04-10 9:03 ` Bruce Richardson
2019-04-10 9:43 ` [dpdk-dev] " Luca Boccassi
2019-04-10 9:43 ` Luca Boccassi
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=60afc83fc723050914d617461607a9c5a72d3017.camel@debian.org \
--to=bluca@debian.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=mdr@ashroe.eu \
--cc=techboard@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).