From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [vmxnet3-usermap PATCH 07/16] pkg: add recipe for RPM Date: Wed, 02 Apr 2014 12:08:47 +0200 Message-ID: <1559189.Xkxy3b07km@xps13> References: <1391529271-24606-1-git-send-email-thomas.monjalon@6wind.com> <1391529271-24606-8-git-send-email-thomas.monjalon@6wind.com> <530DEA9C.8060101@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Thomas Graf Return-path: In-Reply-To: <530DEA9C.8060101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-02-26 14:22, Thomas Graf: > On 02/04/2014 04:54 PM, Thomas Monjalon wrote: > > +BuildRequires: dpdk-core-devel, kernel-devel, kernel-headers > > +Requires: dpdk-core-runtime > > How does the compatibility mapping look like? I assume a given vmxnet3 > version can only be linked against certain dpdk versions? We need to > encode that mapping in the spec file somehow. Since vmxnet3-usermap-1.1, any dpdk >= 1.3 is supported. But RPM packaging is not supported for these old versions. So do you think it's needed to encode a restriction for these old versions? -- Thomas