diff options
Diffstat (limited to 'general-concepts/ebuild-revisions/text.xml')
| -rw-r--r-- | general-concepts/ebuild-revisions/text.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml index 9ddc39f..012745f 100644 --- a/general-concepts/ebuild-revisions/text.xml +++ b/general-concepts/ebuild-revisions/text.xml @@ -17,12 +17,16 @@ 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 <d/> by substantial, we generally mean "something for which many users would want to upgrade". This is usually for bugfixes. +For any such revision bump, the new ebuild should be based on the +previous revision to ensure that fixes aren't dropped accidentally. </p> <p> 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. +In particular, this applies if the package has a substantial compilation +time; developers should use their best judgement in these circumstances. </p> <important> |