[aur-general] Automatic package version

Eli Schwartz eschwartz at archlinux.org
Fri Oct 26 18:14:06 UTC 2018

On 10/26/18 2:07 PM, Shay Gover via aur-general wrote:
>> First thing coming to mind: Did you possibly forget to update the .SRCINFO
>> file?
> Hoe do I update it from the PKGBUILD itself?

The PKGBUILD format is by definition separate from the .SRCINFO, you
don't update it automatically by the PKGBUILD.

You update it separately. The general process is described here:

The "aurpublish" package available in the community repositories can do
this for you.

>> The package is not *supposed* to
>> show an updated version in the AUR, that's the whole point of a pkgver()
>> function.
>> So how does the automatic versioning suppose to work?

It already does work. You download the PKGBUILD from the AUR, and use it
to build a package. A pkgver() function *allows* the package to be newer
than advertised in the AUR.

It's okay for a package to be newer than advertised. That's how all
*-git packages work, by design.

>> P.S. There's no such thing as a pkgrel() function.
> Good to know. Since I need it, What can I do?

I assert that you do not need it.

The pkgver is supposed to be set by the version of the software itself.
The pkgrel is supposed to be the version of the PKGBUILD, and every time
the pkgver gets updated, the pkgrel resets back to "1".

See https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel

An "automatic" pkgrel violates the fundamental purpose of having a
pkgrel in the first place.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20181026/6f226a0f/attachment.asc>

More information about the aur-general mailing list