DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/4] recipes for RPM packages
Date: Wed, 30 Apr 2014 11:22:18 -0400	[thread overview]
Message-ID: <20140430152217.GA13937@localhost.localdomain> (raw)
In-Reply-To: <2579041.G0rVZgHGXT@xps13>

On Wed, Apr 30, 2014 at 01:09:38PM +0200, Thomas Monjalon wrote:
> 2014-04-30 06:52, 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.
> > 
> > You should merge these into a single spec file so that you only have to
> > build once.  That also cleans up the need to adjust the version information
> > in the spec file once, and build packages all get the same versioning.
> 
> The 4 spec files are used to build 4 different git trees with their own 
> versioning:
> 	http://dpdk.org/browse
> So I think it's saner to keep them in their repository.
> 
Ah, I thought these were the pmds that you were building that exist in
dpdk/lib/librte_<vmxnet3|virtio>, etc.

Yeah, if they're separate git trees, they can be separate specs.  That said
though, it strongly begs the question as to why you are keeping open source pmds
outside of the dpdk library?  That really doesn't make much sense,  whats
preventing that integration (followed by the integration of the spec files)?

Neil

> -- 
> Thomas
> 

  reply	other threads:[~2014-04-30 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  0:46 Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [PATCH v2 1/4] pkg: add recipe for RPM Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [memnic PATCH v2 2/4] " Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [vmxnet3-usermap PATCH v2 3/4] " Thomas Monjalon
2014-04-30  0:46 ` [dpdk-dev] [virtio-net-pmd PATCH v2 4/4] " Thomas Monjalon
2014-04-30 10:52 ` [dpdk-dev] [PATCH v2 0/4] recipes for RPM packages Neil Horman
2014-04-30 11:09   ` Thomas Monjalon
2014-04-30 15:22     ` Neil Horman [this message]
2014-05-01  6:53       ` Thomas Monjalon
2014-05-01 10:28         ` Neil Horman
2014-05-01 15:13           ` Thomas Monjalon
2014-05-01 13:14 ` Neil Horman
2014-05-01 21:15   ` Thomas Monjalon

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=20140430152217.GA13937@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --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).