Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
To: Nathan Chancellor <nathan@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Christian Heusel" <christian@heusel.eu>,
	"Nicolas Schier" <nsc@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: pacman-pkg: make "rc" releases adhere to pacman versioning scheme
Date: Fri, 15 May 2026 13:18:15 +0200	[thread overview]
Message-ID: <2fe04523-168b-40d6-bba1-9b1d57939e0d@freenet.de> (raw)
In-Reply-To: <5d5f8ee1-9615-4624-9606-97a6d0943785@freenet.de>

On 5/14/26 23:46, Viktor Jägersküpper wrote:
> On 5/14/26 15:19, Nathan Chancellor wrote:
>> On Thu, 14 May 2026 01:17:29 +0200, Viktor Jägersküpper <viktor_jaegerskuepper@freenet.de> wrote:
>>> diff --git a/scripts/package/PKGBUILD b/scripts/package/PKGBUILD
>>> index 452374d63c24..fe629074b4e8 100644
>>> --- a/scripts/package/PKGBUILD
>>> +++ b/scripts/package/PKGBUILD
>>> @@ -10,7 +10,7 @@ for pkg in $_extrapackages; do
>>>  	pkgname+=("${pkgbase}-${pkg}")
>>>  done
>>>  
>>> -pkgver="${KERNELRELEASE//-/_}"
>>> +pkgver="$(echo "${KERNELRELEASE}" | sed 's/-rc/rc/;s/-/_/g')"
>>
>> Sashiko notes [1] (with a contrived example) that this could result in
>> custom localversions being matched and adjusted. While I don't think it
>> is that big of a deal given how specific the example is, it takes little
>> effort to make the match more restrictive to make such a situation less
>> likely:
>>
>>   pkgver="$(echo "${KERNELRELEASE}" | sed 's/-\(rc[0-9]\+\)/\1/;s/-/_/g')"
>>
>> [1]: https://sashiko.dev/#/patchset/20030
> 
> I agree this is much better. Actually I should have looked at the
> script "mkdebian" for Debian packages which has this line:
> 
> upstream_version=$("${srctree}/scripts/setlocalversion" --no-local "${srctree}" | sed 's/-\(rc[1-9]\)/~\1/')
> 
> This is incorrect for the (hopefully rare) case that we have 10 or more
> "rc" releases, but that can be fixed in another patch.
I was confused, this code for Debian packages should be fine.

Viktor

      reply	other threads:[~2026-05-15 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 23:17 [PATCH] kbuild: pacman-pkg: make "rc" releases adhere to pacman versioning scheme Viktor Jägersküpper
2026-05-14 11:31 ` Thomas Weißschuh
2026-05-14 13:19 ` Nathan Chancellor
2026-05-14 21:46   ` Viktor Jägersküpper
2026-05-15 11:18     ` Viktor Jägersküpper [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=2fe04523-168b-40d6-bba1-9b1d57939e0d@freenet.de \
    --to=viktor_jaegerskuepper@freenet.de \
    --cc=christian@heusel.eu \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --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