From: Jan Blunck <jblunck@infradead.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>, dev <dev@dpdk.org>,
"cjcollier@linuxfoundation.org" <cjcollier@linuxfoundation.org>,
ricardo.salveti@linaro.org,
Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v2] mk: Provide option to set Major ABI version
Date: Fri, 17 Mar 2017 10:16:47 +0100 [thread overview]
Message-ID: <CALe+Z03Kua0h_RG5jm_e28Ajeuy4L_JyAdxxfDWtApf_G1Htug@mail.gmail.com> (raw)
In-Reply-To: <CAATJJ0+YuBTHc+a+ejGO-gDQRx4DGEVMYhaBrU1UGoUDzM_e=A@mail.gmail.com>
On Fri, Mar 17, 2017 at 9:27 AM, Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
>
> On Thu, Mar 16, 2017 at 6:19 PM, Thomas Monjalon <thomas.monjalon@6wind.com>
> wrote:
>>
>> Not sure about how it can be used in distributions, but it does not hurt
>> to provide the config option.
>> Are you going to link applications against a fixed DPDK version for
>> every libraries?
>
>
> Kind of yes - we can still update "inside" a major version e.g. stable
> releases just fine.
> That helps a lot transitioning from one to the next release.
Exactly. It enables me to roll out a new major release without being
blocked on the (external) consumers to pick up the changes. Now I can
do this one by one with reduced risk because the runtimes are clearly
separated.
> And I already heard that even other downstreams are using it to simplify
> their dependencies.
>
Downstream?! Pha! ;)
next prev parent reply other threads:[~2017-03-17 9:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:52 [dpdk-dev] Further fun with ABI tracking Christian Ehrhardt
2017-02-14 16:19 ` Bruce Richardson
2017-02-14 20:31 ` Jan Blunck
2017-02-22 13:12 ` Christian Ehrhardt
2017-02-22 13:24 ` [dpdk-dev] [PATCH] mk: Provide option to set Major ABI version Christian Ehrhardt
2017-02-28 8:34 ` Jan Blunck
2017-03-01 9:31 ` Christian Ehrhardt
2017-03-01 9:34 ` [dpdk-dev] [PATCH v2] " Christian Ehrhardt
2017-03-01 14:35 ` Jan Blunck
2017-03-16 17:19 ` Thomas Monjalon
2017-03-17 8:27 ` Christian Ehrhardt
2017-03-17 9:16 ` Jan Blunck [this message]
2017-02-23 18:48 ` [dpdk-dev] Further fun with ABI tracking Ferruh Yigit
2017-02-24 7:32 ` Christian Ehrhardt
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=CALe+Z03Kua0h_RG5jm_e28Ajeuy4L_JyAdxxfDWtApf_G1Htug@mail.gmail.com \
--to=jblunck@infradead.org \
--cc=christian.ehrhardt@canonical.com \
--cc=cjcollier@linuxfoundation.org \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
--cc=ricardo.salveti@linaro.org \
--cc=thomas.monjalon@6wind.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).