Re: [PATCH] kbuild: deb-pkg: allow to set package name version

[Nicolas Schier <nsc@kernel.org>]

On Tue, Oct 20, 2026 at 11:16:28PM +0200, Guido Günther wrote:
> Hi Nicolas,
> On Tue, Oct 20, 2026 at 10:02:25PM +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.
> 
> The source and the binary package names can already differ due to the
> `KDEB_SOURCENAME` variable (and we're making use of that).
> 
> What this patch adds is the ability to control the suffix so we can
> e.g. build a `linux-ng-foo` and a `linux-stable-bar` instead of having a
> linux-image-7.3.17, linux-image-7.3.18 (or with git versions or …). It's
> just about having a bit more control over the generated binary package
> names so we can decide what replaces what on upgrades.
> 
> I have tested the patch with and without setting KDEB_PKGNAMEVERSION.
> Without setting this variable nothing should change for existing users.

Ack, thanks for clarification.  I'll try to review this next week.
Thanks.

-- 
Nicolas