dev.dpdk.org archive mirror
 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: [PATCH v2 0/4] recipes for RPM packages
Date: Thu, 01 May 2014 23:15:18 +0200	[thread overview]
Message-ID: <1872219.v7nppFMGS2@xps13> (raw)
In-Reply-To: <20140501131410.GC14521-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>

2014-05-01 09:14, Neil Horman:
> On Wed, Apr 30, 2014 at 02:46:41AM +0200, Thomas Monjalon wrote:
> > The goal of this patch serie is to be able to package DPDK
> > for RPM-based distributions.
> > 
> > The file naming currently doesn't allow to install different DPDK
> > versions.
> > But the packaging naming should be ready to manage different DPDK versions
> > 
> > having different API/ABI for different applications:
> > 	- dpdk-core has full version in its name to manage API breaking
> > 	- extensions have a number as name suffix to manage PMD API breaking.
> > 
> > When API/ABI will be stable, package names could be simpler.
> > 
> > I suggest to add these .spec files as a starting point for integration
> > in Linux distributions.
> > 
> > Changes since v1:
> > 	- name of .spec file match package name
> > 	- version in package name
> > 	- no static library
> > 	- ldconfig/depmod in scriplets
> > 
> > Thanks for your comments/reviews.
> 
> I understand that this is holding up the 1.6.0r2 release, as well as the
> 1.7.0 integration.  As such, given that my concerns, while valid IMO,
> aren't required for the release:
> 
> Acked-by: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

Applied for dpdk-1.6.0r2, memnic-1.1, vmxnet3-usermap 1.2
and virtio-net-pmd-1.2.

Thanks Neil and other RedHat people for helping in this first step.

-- 
Thomas

      parent reply	other threads:[~2014-05-01 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  0:46 [PATCH v2 0/4] recipes for RPM packages Thomas Monjalon
     [not found] ` <1398818805-18834-1-git-send-email-thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-04-30  0:46   ` [PATCH v2 1/4] pkg: add recipe for RPM Thomas Monjalon
2014-04-30  0:46   ` [memnic PATCH v2 2/4] " Thomas Monjalon
2014-04-30  0:46   ` [vmxnet3-usermap PATCH v2 3/4] " Thomas Monjalon
2014-04-30  0:46   ` [virtio-net-pmd PATCH v2 4/4] " Thomas Monjalon
2014-04-30 10:52   ` [PATCH v2 0/4] recipes for RPM packages Neil Horman
     [not found]     ` <20140430105221.GA27151-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-04-30 11:09       ` Thomas Monjalon
2014-04-30 15:22         ` Neil Horman
     [not found]           ` <20140430152217.GA13937-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-05-01  6:53             ` Thomas Monjalon
2014-05-01 10:28               ` Neil Horman
     [not found]                 ` <20140501102818.GA14521-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-05-01 15:13                   ` Thomas Monjalon
2014-05-01 13:14   ` Neil Horman
     [not found]     ` <20140501131410.GC14521-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-05-01 21:15       ` Thomas Monjalon [this message]

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=1872219.v7nppFMGS2@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 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).