From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 2887EAFDC for ; Wed, 30 Apr 2014 17:22:25 +0200 (CEST) Received: from nat-pool-rdu-u.redhat.com ([66.187.233.203] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1WfWL1-0007bP-QU; Wed, 30 Apr 2014 11:22:27 -0400 Date: Wed, 30 Apr 2014 11:22:18 -0400 From: Neil Horman To: Thomas Monjalon Message-ID: <20140430152217.GA13937@localhost.localdomain> References: <1398818805-18834-1-git-send-email-thomas.monjalon@6wind.com> <20140430105221.GA27151@hmsreliant.think-freely.org> <2579041.G0rVZgHGXT@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2579041.G0rVZgHGXT@xps13> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 0/4] recipes for RPM packages X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2014 15:22:25 -0000 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_, 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 >