All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Heads up: Fedora packaging plans
Date: Mon, 19 May 2014 12:11:35 +0200	[thread overview]
Message-ID: <1446205.rSbWAAsRtd@xps13> (raw)
In-Reply-To: <20140513190840.GB31172-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>

Hi Neil,

Thanks for sharing your progress.

My main concerns are about naming and extensions.
We must keep "dpdk-core" naming in order to distinguish it from PMD 
extensions. And then, packaging of memnic and non-uio paravirtualization PMDs 
(virtio/vmxnet3) are missing.

2014-05-13 15:08, Neil Horman:
> My current effort to do so.  I've made some changes from the stock spec file
> included in dpdk:

We should try to get .spec for Fedora and in-tree .spec as common as possible.
There are probably some things to push.

> * Modified the version and release values to be separate from the name.  I
> did some reading on requirements for packaging and it seems we can be a bit
> more lax with ABI version on a pre-release I think, so I setup the N-V-R to
> use pre-release conventions, which makes sense, give that this is a 1.7.0
> pre-release.  The git tag on the relase value will get bumped as we move
> forward in the patch series.

I thought that we should put version in the name, in order to be able to 
install many versions together. How is it handled by yum?

> * Added config files to match desired configs for Fedora (i.e. disabled
> PMD's that require out of tree kernel modules

It would be clearer to make your configuration changes with "sed -i".
In a near future we would probably need a "configure" script to do it.

So you don't package igb_uio but you build it because there is no option to 
disable it currently. We should add such option.

> * Moved the package target directories to include N-V of the package in the
> path names.  This allows for multiple versions of the dpdk to be installed
> in parallel (I.e. dpdk-1.7.0 files are in /lib/dpdk-1.7.0,
> /usr/include/dpdk-1.7.0, etc).  This is how java packages allow for
> multiple version installs, and makes sense given ABI instability in dpdk. 
> It will require that developers add some -I / -L paths to their makefiles
> to pull the proper version, but I think thats a fair tradeoff.

I don't see version for include directory and bin directory (testpmd).

Thanks
-- 
Thomas

  parent reply	other threads:[~2014-05-19 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 19:08 Heads up: Fedora packaging plans Neil Horman
     [not found] ` <20140513190840.GB31172-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-05-13 22:46   ` Vincent JARDIN
     [not found]     ` <5372A0CE.6080109-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-05-14 10:54       ` Neil Horman
2014-05-19 10:11   ` Thomas Monjalon [this message]
2014-05-19 13:18     ` Neil Horman
     [not found]       ` <20140519131855.GA2215-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-05-19 16:28         ` Thomas Monjalon
2014-05-19 16:48           ` Neil Horman

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=1446205.rSbWAAsRtd@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.