From: maximilian attems <max@stro.at>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 0/5] Improve flexibility of deb-pkg target
Date: Wed, 1 Apr 2009 22:24:31 +0200 [thread overview]
Message-ID: <20090401202431.GE3901@baikonur.stro.at> (raw)
In-Reply-To: <200904012133.37387.elendil@planet.nl>
On Wed, Apr 01, 2009 at 09:33:36PM +0200, Frans Pop wrote:
> Hi Sam,
>
> This series of patches aims to make the deb-pkg target more flexible.
> I've been using these patches for the past year or so and they've greatly
> improved my workflow for kernel testing on 4 different architectures
> (2 cross-compiled).
>
> The last 2 patches I've submitted before (in Feb. 2008) but were not
> applied as you had some questions. This new series has improved versions
> and I'll address your questions below.
>
> [1/5] deb-pkg: minor general improvements in builddeb script
> [2/5] deb-pkg: fix 'file not found' error when building .deb package for arm
>
> These first 2 patches are minor improvements and fixes.
>
> [3/5] deb-pkg: pass Debian maintainer script parameters to packaging hook scripts
>
> This allows to make hook scripts more specific differentiate their
> behavior for e.g. package installation, removal or upgrade. It's very
> much Debian specific.
>
> [4/5] deb-pkg: allow to specify a custom revision for .deb packages
>
> This has helped me to use a different versioning system for bisections
> than for "regular" builds. Note that this does not affect the kernel
> version (which is part of the package name), but only the version of
> the generated .deb package itself.
>
> [5/5] deb-pkg: allow alternative hook scripts directory in .deb packages
argh none of those apply on top of those that i just sent in,
will nevertheless review them.
prev parent reply other threads:[~2009-04-01 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 19:33 [PATCH 0/5] Improve flexibility of deb-pkg target Frans Pop
2009-04-01 19:38 ` [PATCH 4/5] Frans Pop
2009-04-01 19:42 ` [PATCH 1/5] deb-pkg: minor general improvements in builddeb script Frans Pop
2009-04-01 21:38 ` maximilian attems
2009-04-01 19:43 ` [PATCH 2/5] deb-pkg: fix 'file not found' error when building .deb package for arm Frans Pop
2009-04-01 19:43 ` [PATCH 3/5] deb-pkg: pass Debian maintainer script parameters to packaging hook scripts Frans Pop
2009-04-01 21:41 ` maximilian attems
2009-04-01 19:43 ` [PATCH 5a/5] deb-pkg: allow alternative hook scripts directory in .deb packages Frans Pop
2009-04-01 21:42 ` maximilian attems
2009-04-01 19:44 ` [PATCH 5b/5] " Frans Pop
2009-04-01 21:43 ` maximilian attems
2009-04-01 20:24 ` maximilian attems [this message]
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=20090401202431.GE3901@baikonur.stro.at \
--to=max@stro.at \
--cc=elendil@planet.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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).