On 1 April 2011 08:12, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
I've seen (in the past) various packages on the AUR which jumped by 3 or 4 pkgrels in a very short period of time. Sometimes it happens like this:-
1. Maintainer changes something and breaks the package with pkgrel=2 2. Bug reported on comments. Maintainer reverts change and makes pkgrel=3
It's really very simple - you only need to remember this: Whenever the resulting binary changes (in an important way) for the user, you bump pkgrel. Examples: * Changing pkgdesc -> do NOT bump (unless it's severely wrong or something) * Changing deps -> bump * Changing makedeps -> do NOT bump, ever * Changing optdeps -> do NOT bump (unless very important functionality provided) * Changing build stuff (i.e changing PKGBUILD but no change to resulting binary) -> do NOT bump If in doubt about more scenarios, please describe them. -- GPG/PGP ID: 8AADBB10