From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Chris Wright <chrisw@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 03/16] pkg: add recipe for RPM
Date: Wed, 02 Apr 2014 11:01:49 +0200 [thread overview]
Message-ID: <4232273.mks7Rollq1@xps13> (raw)
In-Reply-To: <20140224165208.GF27503@x220.localdomain>
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.
> > +ExclusiveArch: i686, x86_64
> > +%define target %{_arch}-default-linuxapp-gcc
>
> What is this for?
Multi-targets builds are supported in DPDK Makefiles. So the target must be
explicited when building.
Is it OK to define such variable here?
> > +%description
> > +Dummy main package. Make only subpackages.
>
> I think the core package should have the .so, the -devel package w/
> headers, and no -static package. Including a .a file is discouraged in
> Fedora
OK
> > +%package core-runtime
>
> perhaps just 'runtime'
[...]
> > +%package core-devel
>
> name this devel
No, dpdk-core is a name to differentiate the main component and the extensions
such as dpdk-memnic.
So we should have dpdk-core and dpdk-core-devel. Do you agree?
> > +# debuginfo packaging is broken
> > +%define debug_package %{nil}
>
> Can you add a better comment why it's broken?
Yes, I think it's due to direct use of ld linker.
> > +make O=%{target} T=%{target} config
>
> Did you try to update the build system to output into $RPM_BUILD_ROOT
> directly? It's much preferred compared to the cp/rmdir below
Probably we could change the build system but it should be another patch.
> > +%install
> > +rm -rf %{buildroot}
> > +make O=%{target} DESTDIR=%{destdir}
>
> Why make again (IOW, why not in %build section)?
This one is for installing files only. Isn't it the role of %install?
> > +mv %{destdir}/%{target}/kmod/*.ko %{buildroot}%{moddir}
>
> Normally I'd use install command (-d will create directories)
Yes but here the strategy is to dispatch some files and keep the remaining
ones in %{datadir}.
Thanks for the review
--
Thomas
next prev parent reply other threads:[~2014-04-02 9:00 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 15:54 [dpdk-dev] [PATCH 00/16] recipes for RPM packages Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [PATCH 01/16] tools: rename pci_unbind script Thomas Monjalon
2014-02-24 16:03 ` Chris Wright
2014-03-20 17:06 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [PATCH 02/16] virtio: rename library Thomas Monjalon
2014-02-24 16:05 ` Chris Wright
2014-03-20 17:06 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [PATCH 03/16] pkg: add recipe for RPM Thomas Monjalon
2014-02-24 16:29 ` Chris Wright
2014-02-24 16:52 ` Chris Wright
2014-04-02 9:01 ` Thomas Monjalon [this message]
2014-04-02 11:11 ` Thomas Graf
2014-02-26 13:07 ` Thomas Graf
2014-02-26 16:19 ` Chris Wright
2014-04-02 9:53 ` Thomas Monjalon
2014-04-02 11:04 ` Thomas Graf
2014-04-02 11:29 ` Neil Horman
2014-02-04 15:54 ` [dpdk-dev] [vmxnet3-usermap PATCH 04/16] pmd: add make help Thomas Monjalon
2014-02-24 18:17 ` Chris Wright
2014-03-26 21:59 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [vmxnet3-usermap PATCH 05/16] pmd: allow to build outside of the source directory Thomas Monjalon
2014-02-24 18:13 ` Chris Wright
2014-03-26 21:59 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [vmxnet3-usermap PATCH 06/16] pmd: allow to install lib and doc Thomas Monjalon
2014-03-26 22:00 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [vmxnet3-usermap PATCH 07/16] pkg: add recipe for RPM Thomas Monjalon
2014-02-26 13:22 ` Thomas Graf
2014-04-02 10:08 ` Thomas Monjalon
2014-04-02 11:07 ` Thomas Graf
2014-02-04 15:54 ` [dpdk-dev] [virtio-net-pmd PATCH 08/16] pmd: fix initialization of Tx queue header Thomas Monjalon
2014-03-27 8:23 ` Olivier MATZ
2014-03-27 9:34 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [virtio-net-pmd PATCH 09/16] mk: minor fixes Thomas Monjalon
2014-03-27 8:26 ` Olivier MATZ
2014-03-27 9:35 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [virtio-net-pmd PATCH 10/16] mk: allow to build outside of the source directory Thomas Monjalon
2014-03-27 8:31 ` Olivier MATZ
2014-03-27 9:35 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [virtio-net-pmd PATCH 11/16] mk: allow to install lib and doc Thomas Monjalon
2014-03-27 8:32 ` Olivier MATZ
2014-03-27 9:35 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [virtio-net-pmd PATCH 12/16] pkg: add recipe for RPM Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [memnic PATCH 13/16] pmd: rename doc when installing Thomas Monjalon
2014-03-27 8:36 ` Olivier MATZ
2014-03-27 10:29 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [memnic PATCH 14/16] pmd: fix doc uninstalling Thomas Monjalon
2014-03-27 8:45 ` Olivier MATZ
2014-03-27 10:30 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [memnic PATCH 15/16] pmd: remove useless makefile variables Thomas Monjalon
2014-03-27 8:45 ` Olivier MATZ
2014-03-27 10:30 ` Thomas Monjalon
2014-02-04 15:54 ` [dpdk-dev] [memnic PATCH 16/16] pkg: add recipe for RPM 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=4232273.mks7Rollq1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=chrisw@redhat.com \
--cc=dev@dpdk.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).