summaryrefslogtreecommitdiffstats
path: root/RELEASE-NOTES
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2007-06-13 08:08:55 +0000
committerZac Medico <zmedico@gentoo.org>2007-06-13 08:08:55 +0000
commit34b402317b6b4d4892ea2f7ac99b27a91afc1b2f (patch)
treed157bb828f75ee2a99e1d26ebceeae3d60273c9c /RELEASE-NOTES
parenta133cb89d5279df7febcd0c8ab3890e2ccfb897a (diff)
downloadportage-34b402317b6b4d4892ea2f7ac99b27a91afc1b2f.tar.gz
portage-34b402317b6b4d4892ea2f7ac99b27a91afc1b2f.tar.bz2
portage-34b402317b6b4d4892ea2f7ac99b27a91afc1b2f.zip
Add a note about the new unmerge-orphans behavior.
svn path=/main/trunk/; revision=6831
Diffstat (limited to 'RELEASE-NOTES')
-rw-r--r--RELEASE-NOTES9
1 files changed, 9 insertions, 0 deletions
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index 01507f0c2..faa580316 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -18,6 +18,15 @@ portage-2.2
For packages that don't specify any other KEYWORDS you can use the new ** token
as documented in portage(5) to disable KEYWORDS filtering completely.
+portage-2.1.3
+==================================
+
+* The unmerge process will remove any file that is not claimed by another
+ package in the same slot and is not protected by CONFIG_PROTECT, even if the
+ modification time or checksum differs from the file that was originally
+ installed. The old behavior is still available by adding -unmerge-orphans
+ to FEATURES.
+
portage-2.1.2
==================================