DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] libdpdk upstream changes for ecosystem best practices
Date: Wed, 2 Sep 2015 09:01:25 -0700	[thread overview]
Message-ID: <20150902090125.0579e052@urahara> (raw)
In-Reply-To: <4202381.KjbOiZhtub@xps13>

On Wed, 02 Sep 2015 16:18:33 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> Hi,
> 
> 2015-09-02 14:49, Robie Basak:
> > Hi,
> > 
> > We’re looking at packaging DPDK in Ubuntu. We’d like to discuss upstream
> 
> Nice

This matches what we do internally. I was heading towards making this
a real Debian package. Since Debian is more free and is a superset
of Ubuntu.

> 
> > changes to better integrate DPDK into Linux distributions. Here’s a
> > summary of what we need:
> > 
> >  1) Define one library ABI (soname and sover) that we can use instead of the
> >     split build.
> > 
> >  2) Fix #includes so we don't have to include config.h
> > 
> >  3) Put headers into /usr/include/dpdk instead of /usr/include
> > 
> > You can see our current packaging progress at
> > https://git.launchpad.net/~ubuntu-server/dpdk/log/?h=ubuntu-wily and a
> 
> Thanks for sharing

I have made basically the same decisions. Target is /usr/include/dpdk
and the library version comes from rte config. It seems more logical
to make the library shared object version equal the major version
of DPDK (ie 2) rather than having shared object and source versions
diverge.

Just updating to 2.1 packaging now, will send patches.

  reply	other threads:[~2015-09-02 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 13:49 Robie Basak
2015-09-02 14:18 ` Thomas Monjalon
2015-09-02 16:01   ` Stephen Hemminger [this message]
2015-09-18 10:39   ` Robie Basak
2015-09-02 23:47 ` Nikita Kozlov

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=20150902090125.0579e052@urahara \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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).