diff options
authorMark Loeser <halcy0n@gentoo.org>2006-02-27 15:51:45 +0000
committerMark Loeser <halcy0n@gentoo.org>2006-02-27 15:51:45 +0000
commit296c57d3e177875dea9fc69cdc21d25befabce01 (patch)
tree1b1b77add04d0055420e297db39a41b1a8060773 /general-concepts/ebuild-revisions/text.xml
parentAdd some more of general-concepts (diff)
Add some more pages. The Makefile now generates the png's at build time, so we don't need the PNGs in the repo anymore
git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/devmanual/trunk@7 176d3534-300d-0410-8db8-84e73ed771c3
Diffstat (limited to 'general-concepts/ebuild-revisions/text.xml')
1 files changed, 35 insertions, 0 deletions
diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml
new file mode 100644
index 0000000..51c109f
--- /dev/null
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -0,0 +1,35 @@
+<?xml version="1.0"?>
+<guide self="general-concepts/ebuild-revisions/">
+<title>Ebuild Revisions</title>
+Ebuilds may have a Gentoo revision number associated with them. This is a
+<c>-rX</c> suffix, where <c>X</c> is an integer -- see `File Naming Rules`_. This
+component must only be used for Gentoo changes, not upstream releases. By
+default, <c>-r0</c> is implied and should not be specified manually.
+Ebuilds should have their <c>-rX</c> incremented whenever a change is made which
+will make a substantial difference to what gets installed by the package -- by
+substantial, we generally mean "something for which many users would want to
+upgrade". This is usually for bugfixes.
+Simple compile fixes do <b>not</b> warrant a revision bump; this is because they do
+not affect the installed package for users who already managed to compile it.
+Small documentation fixes are also usually not grounds for a new revision.
+When doing a revision bump, the usual rules about dropping to <c>~arch</c> apply.
+See `Keywording on Upgrades`_.