From: Nicolas Schier <nsc@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] kbuild: deb-pkg: Allow packages to be excluded from bindeb-pkg
Date: Sun, 23 Nov 2025 21:34:23 +0100 [thread overview]
Message-ID: <aSNvz2rzpt2PE9t8@levanger> (raw)
In-Reply-To: <20251123183647.76559-1-maz@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Sun, Nov 23, 2025 at 06:36:47PM +0000, Marc Zyngier wrote:
> The bindeb-pkg target generates a number of individual packages:
> the kernel package itself, the debug package, the kernel and libc
> header packages.
>
> It is at times useful to not generate all the packages, such as
> the debug package, even if the kernel configuration has CONFIG_DEBUG.
>
> For this purpose, let the user provide a DEB_EXCLUDE_PKG environment
> variable that can contain exclusion patterns for some of the build
> artefacts. This saves precious cycles when repeatedly building packages
> for testing purposes, where not all packages are strictly necessary.
>
> The default behaviour, with no variable defined, is of course unchanged.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
thanks for your suggestion. Could you please check whether the usual
Debian build profiles are sufficient for your needs, e.g.:
DEB_BUILD_PROFILES="pkg.linux-upstream.nokernelheaders pkg.linux-upstream.nokerneldbg" make bindeb-pkg
I do like that we have the Debian build profiles [1] mechanism here, and
would rather extend it, if neccessary, instead of implementing a
different approach additionally.
Kind regards,
Nicolas
[1]: https://wiki.debian.org/BuildProfileSpec
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-23 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 18:36 [PATCH] kbuild: deb-pkg: Allow packages to be excluded from bindeb-pkg Marc Zyngier
2025-11-23 20:34 ` Nicolas Schier [this message]
2025-11-23 21:47 ` Marc Zyngier
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=aSNvz2rzpt2PE9t8@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nathan@kernel.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