[patch] 0001-Document-necessity-to-revbump-on-RDEPEND-changes.patch

0001-Document-necessity-to-revbump-on-RDEPEND-changes.patch (text/plain), 1.36 KB, created by Julian Ospald on 2015-09-15 10:49:29 UTC

From 711ac552ff1145f5a21f8b5e0db5ab6f67ef72dd Mon Sep 17 00:00:00 2001
From: Julian Ospald <[e-mail]>
Date: Tue, 15 Sep 2015 12:46:30 +0200
Subject: [PATCH] Document necessity to revbump on RDEPEND changes

This is related to the upcoming dynamic-dependencies removal in
portage which is an undocumented feature and not part of PMS. Thus,
developers should never rely on it.
---
 general-concepts/ebuild-revisions/text.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/general-concepts/ebuild-revisions/text.xml b/general-concepts/ebuild-revisions/text.xml
index 012745f..2d44146 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -17,6 +17,9 @@ 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.
+Revision bumps are also necessary whenever runtime dependencies change, because
+that is the only reliable way to update the user's VDB (where information
+about installed packages is stored) and ensure it is in a consistent state.
 For any such revision bump, the new ebuild should be based on the
 previous revision to ensure that fixes aren't dropped accidentally.
 </p>
-- 
2.5.2