[aur-general] Incrementing pkgrel
Hi all, what is the common practice when facing a PKGBUILD update that does not change the final binary package nor the dependency tree (let's say, a type in an "echo" message or a wrong # Contributor: line)? Do I have to increment the pkgrel value anyway? This is the guilty PKGBUILD: it is pretty straightforward but... just in case I have made some other stupid mistake. http://aur.archlinux.org/packages/gtk2panel/gtk2panel/PKGBUILD Thanks in advance. -- Nicola
On Fri, Aug 7, 2009 at 3:48 PM, Nicola Fontana <ntd@entidi.it> wrote:
Hi all,
what is the common practice when facing a PKGBUILD update that does not change the final binary package nor the dependency tree (let's say, a type in an "echo" message or a wrong # Contributor: line)? Do I have to increment the pkgrel value anyway?
This is the guilty PKGBUILD: it is pretty straightforward but... just in case I have made some other stupid mistake.
http://aur.archlinux.org/packages/gtk2panel/gtk2panel/PKGBUILD
Thanks in advance. -- Nicola
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
Il giorno Fri, 7 Aug 2009 15:51:29 -0700 Smartboy <smartboyathome@gmail.com> ha scritto:
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
Quick and clean: thank you.
Am Fri, 7 Aug 2009 15:51:29 -0700 schrieb Smartboy <smartboyathome@gmail.com>:
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
That's not true. AUR will also update packages without incrementing the pkgrel. But the AUR scripts like yaourt and aurbuild won't automatically install the updated packages if the pkgrel isn't incremented. But I don't know the official policy for this. A few days ago I had to do small changes at a PKGBUILD. Because it wasn't a real update and didn't affect already installed packages, I didn't want to force the users to recompile the package. So I updated the PKGBUILD without incrementing the pkgrel. Heiko
On Fri, Aug 7, 2009 at 4:51 PM, Heiko Baums <lists@baums-on-web.de> wrote:
Am Fri, 7 Aug 2009 15:51:29 -0700 schrieb Smartboy <smartboyathome@gmail.com>:
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
That's not true. AUR will also update packages without incrementing the pkgrel. But the AUR scripts like yaourt and aurbuild won't automatically install the updated packages if the pkgrel isn't incremented.
But I don't know the official policy for this.
A few days ago I had to do small changes at a PKGBUILD. Because it wasn't a real update and didn't affect already installed packages, I didn't want to force the users to recompile the package. So I updated the PKGBUILD without incrementing the pkgrel.
Heiko
That is odd, when I try to upload a PKGBUILD without updating teh pkgrel, the PKGBUILD stays the same. Though, it could be me forgetting to clear the cache. :P
2009/8/8 Smartboy <smartboyathome@gmail.com>:
On Fri, Aug 7, 2009 at 4:51 PM, Heiko Baums <lists@baums-on-web.de> wrote:
Am Fri, 7 Aug 2009 15:51:29 -0700 schrieb Smartboy <smartboyathome@gmail.com>:
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
That's not true. AUR will also update packages without incrementing the pkgrel. But the AUR scripts like yaourt and aurbuild won't automatically install the updated packages if the pkgrel isn't incremented.
But I don't know the official policy for this.
A few days ago I had to do small changes at a PKGBUILD. Because it wasn't a real update and didn't affect already installed packages, I didn't want to force the users to recompile the package. So I updated the PKGBUILD without incrementing the pkgrel.
Heiko
That is odd, when I try to upload a PKGBUILD without updating teh pkgrel, the PKGBUILD stays the same. Though, it could be me forgetting to clear the cache. :P
I've noticed that the PKGBUILD is same when you look at it using your web browser, but it's caused only by caching. After reloading page you will se the new one. Anyway, I'm in favor of not changing pkgrel when the changes doesn't affect the package itself (ie. changes to comments or whitespace changes). If you change pkgrel everyone with yaourt or something like that will recompile the package for nothing.
I think there was a semi-official stance on this. The documentation indicates that pkgrel is to be bumped for updates. If your change is not meant for an update the user wants to see, then there is obviously no need for a pkgrel bump.
Il giorno Sat, 8 Aug 2009 01:51:05 +0200 Heiko Baums <lists@baums-on-web.de> ha scritto:
Am Fri, 7 Aug 2009 15:51:29 -0700 schrieb Smartboy <smartboyathome@gmail.com>:
In order for it to be updated in AUR, you need to at least increment the PKGBUILD's pkgrel by one. Otherwise it won't update it.
That's not true. AUR will also update packages without incrementing the pkgrel. But the AUR scripts like yaourt and aurbuild won't automatically install the updated packages if the pkgrel isn't incremented.
I just updated with the same pkgrel and it worked. Thanks to all. -- Nicola
Nicola Fontana wrote:
Hi all,
what is the common practice when facing a PKGBUILD update that does not change the final binary package nor the dependency tree (let's say, a type in an "echo" message or a wrong # Contributor: line)? Do I have to increment the pkgrel value anyway?
This is the guilty PKGBUILD: it is pretty straightforward but... just in case I have made some other stupid mistake.
http://aur.archlinux.org/packages/gtk2panel/gtk2panel/PKGBUILD
Thanks in advance. if is doesn't affect the binary,basically are only cosmetic changes, i don't increment pkgrel.
-- Ionut
participants (6)
-
Biru Ionut
-
Heiko Baums
-
Lukáš Jirkovský
-
Nicola Fontana
-
Ray Rashif
-
Smartboy