[pacman-dev] pkgrel in VCS packages
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? -- 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);}
On Tue, 2013-05-07 at 10:30 +0200, 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? -- 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);}
You can do it like this: _pkgver=$(your pkgver command) if [[ $_pkgver == $pkgver ]]; then exit 1 else echo $_pkgver fi Cheers, -- Maxime
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.
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
On Tue, 2013-05-07 at 19:19 +1000, Allan McRae wrote:
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
Indeed, I just saw that too. There's no need to trick the pkgver function. Cheers, -- Maxime
Allan McRae
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);}
participants (3)
-
Allan McRae
-
Christian Hesse
-
Maxime Gauduin