> > Date: Fri, 26 Oct 2018 19:09:36 +0100 > From: Konstantin Gizdov <[email protected]> > To: [email protected] > Subject: Re: [aur-general] Automatic package version > Message-ID: <[email protected]> > Content-Type: text/plain; charset="utf-8" > > On 26/10/2018 19:07, Shay Gover via aur-general wrote: > >> Message: 1 > >> Date: Fri, 26 Oct 2018 18:29:59 +0200 > >> From: Michael Kogan <[email protected]> > >> To: "Discussion about the Arch User Repository (AUR)" > >> <[email protected]> > >> Subject: Re: [aur-general] Automatic package version > >> Message-ID: > >> < > >> calsov+bp9ez_v_wfsv5mz9muaringnczxwyyx_1endofkj_...@mail.gmail.com> > >> Content-Type: text/plain; charset="UTF-8" > >> > >> First thing coming to mind: Did you possibly forget to update the > .SRCINFO > >> file? > >> > > Hoe do I update it from the PKGBUILD itself? > > I normally have an alias like this: > > $ which updpkgs > updpkgs: aliased to 'updpkgsums && makepkg --printsrcinfo > .SRCINFO' > > That's from outside the PKGBUILD. I already did that when I uploaded the package a month ago. But since then the package was updated. It's not automatic versioning if I need to update SRCINFO every time.
> 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: > > https://wiki.archlinux.org/index.php/Arch_User_Repository#Uploading_packages > > The "aurpublish" package available in the community repositories can do > this for you. > > > OK. But I'll still need to create a local script that will do that, right? > >> 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. > > You're correct. My fault. :/
