version / pkgver

theking2 · 2011-01-25 19:50:46

When working with thrid party software that is packaged in a AUR PKGBUILD I find it difficult to decide on the version and pacakge release of the package.

Right now I'm attempting to get a SqueezeboxServer package up to date. The developers are at version 7.6.0 build 31827. Now the package might have a different version universe all to gether as startup scripts etc might have to be versioned as well where they are no part of the original software.

How to escape from this predicemant? Use the version of the original software provider? Or use a different versioning alltogether?

j

Last edited by theking2 (2011-01-25 19:51:33)

Inxsible · 2011-01-25 19:53:44

always use the developers versions-pkgrel -- where pkgrel is just a number that you keep incrementing if you ever change the PKGBUILD and the srouce hasn't changed.

If you do not use the dev versions, your package in AUR will be flagged as out of date by some user

theking2 · 2011-01-25 22:15:14

In this case the development team decide to store use version string "7.6" for the folder "7.6.0" for the version string and an additional build number "31827". What number should be used for pkgver?, pkgrel?

Xyne · 2011-01-25 23:06:59

pkgver=7.6.0.31827
pkgrel=1

The PKGBUILD pkgrel variable has nothing to do with the upstream version. It should always be set to 1 when you create a new PKGBUILD or when you bump the pkgver. If you update the PKGBUILD to fix the PKGBUILD itself (e.g. to add a missing dep, but not to update to a new version) then you would bump the pkgrel by 1.

Last edited by Xyne (2011-01-25 23:07:23)

Arch Linux

#1 2011-01-25 19:50:46

version / pkgver

#2 2011-01-25 19:53:44

Re: version / pkgver

#3 2011-01-25 22:15:14

Re: version / pkgver

#4 2011-01-25 23:06:59

Re: version / pkgver

Board footer