From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, Ray Kinsella <mdr@ashroe.eu>
Cc: dev <dev@dpdk.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Olivier Matz <olivier.matz@6wind.com>,
Neil Horman <nhorman@tuxdriver.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Kevin Traynor <ktraynor@redhat.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v8 2/4] doc: changes to abi policy introducing major abi versions
Date: Wed, 6 Nov 2019 10:21:36 +0100 [thread overview]
Message-ID: <CAJFAV8y1Sp3fWXcGkFWwv_ynajOOEXh0qNZW-o9JLrpWvcJ3Yw@mail.gmail.com> (raw)
In-Reply-To: <2325188.Q6BSOo8498@xps>
On Wed, Nov 6, 2019 at 10:06 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> > >> +Libraries marked as ``experimental`` are entirely not considered part of an ABI
> > >> +version, and may change without warning at any time. Experimental libraries
> > >> +always have a major version of ``0`` to indicate they exist outside of
> > >> +ABI Versioning, with the minor version incremented with each ABI change
> > >> +to library.
> > >
> > > It means not all libraries will have the same ABI version.
> > > It is contrary of "ABI version is managed at a project level",
> > > and I don't see a real benefit of a different version number.
> >
> > There is a benefit, major version 0 is a very clear indication that
> > the library exists outside of ABI management.
> > A library isn't in the ABI, until it is in the ABI - an then it gets
> > added to the major version number.
The user must already set ALLOW_EXPERIMENTAL_API when using api from
such a library.
This is visible to him when developping.
On the contrary a 0 ABIVER is an (almost) internal thing.
> >
> > > Anyway, some experimental functions can live inside a library
> > > with a stable ABI version number
> >
> > True, but if an entire library is experimental - let's be crystal
> > clear about that.
Having this special case means that the library soname will contain a .0.
Won't it prevent us from having two versions of dpdk installed?
--
David Marchand
next prev parent reply other threads:[~2019-11-06 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:24 [dpdk-dev] [PATCH v8 0/4] " Ray Kinsella
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 1/4] doc: separate versioning.rst into version and policy Ray Kinsella
2019-11-05 17:37 ` Stephen Hemminger
2019-11-06 16:11 ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 2/4] doc: changes to abi policy introducing major abi versions Ray Kinsella
2019-11-05 17:37 ` Stephen Hemminger
2019-11-06 0:11 ` Thomas Monjalon
2019-11-06 8:49 ` Ray Kinsella
2019-11-06 9:06 ` Thomas Monjalon
2019-11-06 9:21 ` David Marchand [this message]
2019-11-06 9:22 ` Ray Kinsella
2019-11-06 21:07 ` Thomas Monjalon
2019-11-08 14:09 ` Ray Kinsella
2019-11-06 16:12 ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 3/4] doc: updates to versioning guide for " Ray Kinsella
2019-11-05 17:37 ` Stephen Hemminger
2019-11-06 16:13 ` Mcnamara, John
2019-11-05 15:24 ` [dpdk-dev] [PATCH v8 4/4] doc: add maintainer for abi policy Ray Kinsella
2019-11-06 16:13 ` Mcnamara, John
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=CAJFAV8y1Sp3fWXcGkFWwv_ynajOOEXh0qNZW-o9JLrpWvcJ3Yw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.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).