From: maximilian attems <maks@stro.at>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
mmarek <mmarek@suse.cz>,
debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH 2/2] deb-pkg: add source package
Date: Thu, 23 Apr 2015 12:43:58 +0200 [thread overview]
Message-ID: <20150423104358.GR27866@stro.at> (raw)
In-Reply-To: <CAAqcGHnRinMmG++0d02-ANYrdhxod5K3G5qcwxbA7tKOqe+Fjw@mail.gmail.com>
On Thu, Apr 23, 2015 at 12:01:10PM +0300, Riku Voipio wrote:
> On 22 April 2015 at 18:50, maximilian attems <maks@stro.at> wrote:
> >
> > great this is a much requested feature for wider adoption of make
> > deb-pkg. In general acked-by me, just minor comment below.
> >
> > I do not like the BUILD_SOURCE=y variable,
> > I think it should just be like the other scripts and do it by default.
> >
> > What we do need is a target that *only* compiles the linux image.
>
> So a bin-debpkg target in scripts/package/Makefile ?
yes, please.
> >> scripts/package/builddeb | 42 ++++++++++++++++++++++++++++++++++++++++++
> >> 1 file changed, 42 insertions(+)
> >>
> >> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> >> index e397815..3d77fd3 100755
> >> --- a/scripts/package/builddeb
> >> +++ b/scripts/package/builddeb
> >> @@ -272,12 +272,23 @@ On Debian GNU/Linux systems, the complete text of the GNU General Public
> >> License version 2 can be found in \`/usr/share/common-licenses/GPL-2'.
> >> EOF
> >>
> >> +
> >> +build_depends="bc, "
> >> +if [ -n "$BUILD_TOOLS" ]
>
> > why this dual stage?
>
> That variable was introduced in "RFC: builddeb: add linux-tools
> package with perf" [1]. Building perf
> as part of deb-pkg was kind of the major motivation for these series.
With adding the very specific image target, I don't think this variable
is needed.
> >> +then
> >> + build_depends="$build_depends python-dev, libperl-dev, bison, flex, \
> >> +libaudit-dev, libdw-dev, libelf-dev, libiberty-dev, libnewt-dev, autoconf, \
> >> +automake, libtool, libglib2.0-dev, libudev-dev, libwrap0-dev, libiberty-dev, \
> >> +libunwind8-dev [amd64 arm64 i386], libnuma-dev [amd64 arm64 i386 powerpc ppc64 ppc64el] "
>
> > how did you generate this list, this seems bogus to me?!
>
> > python-dev should probably be python
> > why would you need automake?
>
> These are build-depends of linux-tools (perf etc).
Hmm, ok.
> > plus I do seem to miss cpio, kmod.
>
> I'll add kmod and cpio to the non-tools case.
good.
next prev parent reply other threads:[~2015-04-23 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 13:15 [PATCH 1/2] deb-pkg: move setting debarch for a separate function riku.voipio
2015-04-10 13:15 ` [PATCH 2/2] deb-pkg: add source package riku.voipio
2015-04-22 15:50 ` maximilian attems
2015-04-23 9:01 ` Riku Voipio
2015-04-23 10:43 ` maximilian attems [this message]
2015-04-15 12:30 ` [PATCH 1/2] deb-pkg: move setting debarch for a separate function Michal Marek
2015-04-16 13:42 ` [PATCH] deb-pkg: v2: " riku.voipio
2015-04-22 14:45 ` Michal Marek
2015-04-22 15:52 ` maximilian attems
-- strict thread matches above, loose matches on Subject: below --
2015-05-28 9:11 [PATCH 2/2] deb-pkg: add source package riku.voipio
2015-05-31 1:14 ` Ben Hutchings
2015-06-01 8:35 ` Riku Voipio
2015-06-01 12:03 ` Ben Hutchings
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=20150423104358.GR27866@stro.at \
--to=maks@stro.at \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=riku.voipio@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.