From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id A93A06835 for ; Wed, 2 Apr 2014 13:09:56 +0200 (CEST) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s32BBUfq004251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Apr 2014 07:11:30 -0400 Received: from lsx.localdomain (vpn1-7-206.ams2.redhat.com [10.36.7.206]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s32BBQMo029904; Wed, 2 Apr 2014 07:11:27 -0400 Message-ID: <533BF05E.9000904@redhat.com> Date: Wed, 02 Apr 2014 13:11:26 +0200 From: Thomas Graf Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Thomas Monjalon , Chris Wright References: <1391529271-24606-1-git-send-email-thomas.monjalon@6wind.com> <1391529271-24606-4-git-send-email-thomas.monjalon@6wind.com> <20140224165208.GF27503@x220.localdomain> <4232273.mks7Rollq1@xps13> In-Reply-To: <4232273.mks7Rollq1@xps13> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 03/16] pkg: add recipe for RPM 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, 02 Apr 2014 11:09:57 -0000 On 04/02/2014 11:01 AM, Thomas Monjalon wrote: > Hello, > > Sorry for the long delay. > > 2014-02-24 08:52, Chris Wright: >>> pkg/rpm.spec | 143 >> >> This should be dpdk.spec > > Actually it should be dpdk-core.spec. > Since it is a file hosted in the project, is it mandatory to have such naming? > Could you explain why? > When building it with "rpmbuild -ta dpdk.tar.gz", the .spec name has no > importance. You are right, it doesn't matter for external building but this would likely get pointed at in the Fedora package review process. https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Spec_file_name