Arch Linux

Konzertheld

Member

Registered: 2017-03-09

Posts: 18

Changing the pkgver format to include VCS state

Hello,

I adopted a VCS package. The PKGBUILD contains a pkgver in the DATE.rHASH format. The wiki states that it is prefered to include a tag and using one of the functions from the wiki I was indeed able to create a pkgver in a format using a tag. Now I would like to know if it will cause problems if I change it (I need to change the PKGBUILD anyway because of a changed dependency). I would change from 20220914.r26957e0 to 1.0.3.r0.ga43b4c3. Please let me know if that's okay. I noticed the r0 and was skeptical. It seems to come from the git output before the pipe which is: 1.0.3-0-ga43b4c3

Wiki page I am refering to: https://wiki.archlinux.org/title/VCS_pa … elines#Git
I used

git describe --long --tags --abbrev=7 | sed 's/\([^-]*-g\)/r\1/;s/-/./g'

as described under "Using the most recent un-annotated tag reachable from the last commit".

Thanks.

gromit

Package Maintainer (PM)

From: Germany

Registered: 2024-02-10

Posts: 914

Website

Re: Changing the pkgver format to include VCS state

I would change from 20220914.r26957e0 to 1.0.3.r0.ga43b4c3

This only works when using an epoch, as "20220914" would always assumed to be a bigger version than "1".

FabioLolix

Member

Registered: 2021-06-27

Posts: 9

Website

Re: Changing the pkgver format to include VCS state

Hi

> 1.0.3.r0.ga43b4c3. Please let me know if that's okay. I noticed the r0 and was skeptical

That's ok, it mean that there have been 0 revision since the 1.0.3 tag

btw which pkgbuild is?