mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Nicolas Schier" <nsc@kernel.org>,
	"Guido Günther" <agx@sigxcpu.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: deb-pkg: allow to set package name version
Date: Tue, 20 Oct 2026 22:16:22 +0200	[thread overview]
Message-ID: <7bc00156-6723-4987-88bd-9d3451edc8a5@t-8ch.de> (raw)
In-Reply-To: <atfI0Uc3iWSmR49j@levanger>

On 2026-10-20 22:02:25+0200, Nicolas Schier wrote:
> On Mon, Oct 19, 2026 at 09:16:14PM +0200, Guido Günther wrote:
> > Instead of hardcoding ${KERNELRELEASE} in the package name allow
> > the user to override this.
> > 
> > This can be useful if one doesn't want to accumulate different packages
> > for every commit or micro version bump by setting
> > KDEB_PKGNAMEVERSION=7.3 or even KDEB_PKGNAMEVERSION=stable.
> 
> I am not yet convinced, that this is a good idea.  Do you want to
> elaborate a bit more, why you think this is necessary?  Have you tested
> your patch?  I don't like that source package name and binary package
> name divert w/o good reasoning.

FWIW we have something similar for the Arch Linux packaging with
PACMAN_PKGBASE. It is the complement to the proposed patch, as Arch Linux
by default does *not* allow multiple installed kernel packages of a
single type at the same time. PACMAN_PKGBASE allows this.
KDEB_PKGNAMEVERSION would enable the Arch Linux behavior for the Debian
packages. Personally I would have found this convenient in the past.


Thomas

  reply	other threads:[~2026-10-20 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 19:16 Guido Günther
2026-10-20 20:02 ` Nicolas Schier
2026-10-20 20:16   ` Thomas Weißschuh [this message]
2026-10-20 21:16   ` Guido Günther

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=7bc00156-6723-4987-88bd-9d3451edc8a5@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=agx@sigxcpu.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@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

all inboxes | Powered by JetHome®