Allan McRae <[email protected]> on Tue, 2013/05/07 19:19: > On 07/05/13 19:16, Allan McRae wrote: > > On 07/05/13 18:30, Christian Hesse wrote: > >> Hello everybody, > >> > >> I love the new pkgver() function that allows to update pkgver string. > >> However this also sets "pkgrel=1". Most of the time this is ok, but it > >> is problematic for repositories that change very seldom, so a rebuild > >> would get exactly the same version string again and again. > >> > >> Is there any way to workaround this? > >> > > > > I thought the pkgrel did not revert to 1 unless the pkgver changed. > > I was correct - the new pkgrel is only set to 1 if the pkgver changes: > > if [[ -n $newpkgver && $newpkgver != "$pkgver" ]]; then
Uh, you are correct... This was my local build script - it copied the
PKGBUILD before building the package, so pkgver was updated every time.
Still have to think about how to handle this when building AUR packages...
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
signature.asc
Description: PGP signature
