Git-Url: http://git.frugalware.org/gitweb/gitweb.cgi?p=frugalware-current.git;a=commitdiff;h=35f6c143679435e102f8d97a8e735656cf68a6da
commit 35f6c143679435e102f8d97a8e735656cf68a6da Author: Miklos Vajna <[EMAIL PROTECTED]> Date: Tue Apr 29 11:03:54 2008 +0200 docs/security: add versioning rules diff --git a/docs/security.txt b/docs/security.txt index 9da08c5..08a7fe8 100644 --- a/docs/security.txt +++ b/docs/security.txt @@ -57,3 +57,29 @@ can find the filename of the fix. . It's also a good idea to take a look on redhat/gentoo bugzilla. They attach fixes most the time. So it's good to read the secunia mails carefully as you'll always know when the patch is available. + +== Versioning + +We use integers in pkgrels for normal packages, but -stable updates are +different. Here are the cases: + +* If you do a version bump (we refer to them as 'secfix bump' usually in + -stable commit messages), then you need to set pkgrel to 1kalgan1. + +* If you add a security patch, and pkgrel was an integer (let's say '1'), then + you should increment pkgrel to 2kalgan1. + +* If you add a security patch when the pkgrel was already in an XkalganY form, + increment it to XkalganY+1. (Alternatively, you can use X+1kalganY if there + is already a newer version in -current.) + +(Replace kalgan with the current release name, later.) + +This ensures the followings: + +* The version of the security update will be larger than the one in -stable, so + that the package will be upgraded when the user does a pacman-g2 -Syu on + -stable. +* The version of the security update will be smaller than the one in -current, + so that the package will be upgraded when the user upgrades to a new version + (current or new stable). _______________________________________________ Frugalware-git mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-git
