For bug #158931, add some release notes to explain performance penalties for dependen...

svn path=/main/trunk/; revision=5367

diff --git a/NEWS b/NEWS
index d80c27c39b31c9588ba1b1051e20c0a3248a458f..c560d1308957ee1d8450c6fd1d3ee58a1970fb9c 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -13,6 +13,8 @@ portage-2.1.2
 * Dependencies can be satisfied by installed packages that do not have matching
   ebuilds in the portage tree or overlay.
 * Emerge automatically ignores blockers that are made irrelevant by an upgrade.
+* Emerge supports "reverse blocker detection" which means that the blockers of
+  installed packages will always be respected.
 * Emerge builds a complete dependency graph in order to ensure correct merge
   order and detection of circular dependencies.
 * The world and system sets allow automatic update of all installed slots.

diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index c15f922bafd16f995af4cce4951f2eed9819aaa9..26d95a9cdf226b67930bca171a3ad172470ec686 100644 (file)
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -4,6 +4,12 @@ Features/major bugfixes are listed in NEWS
 portage-2.1.2
 ==================================
 
+* Depending on the number of packages installed, users may notice a difference
+  in the time taken for dependency calculations.  This performance penalty is
+  due to the addition of important new features which include the ability to
+  detect reverse blockers, the building of a complete dependency graph, and the
+  ability to use installed packages to satisify dependencies even after their
+  ebuilds have been removed from the portage tree.
 * emerge does not necessarily update build time dependencies that are not
   strictly required.  See the --with-bdeps option in the emerge(1) man page.