From 3931a1e06f5ef8e8b5c0d3d82f2332f6441035c2 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Mon, 12 Jan 2009 08:19:04 +0000 Subject: Bug #253745 - Note that you need to ensure that neither protect-owned nor collision-protect are enabled if you want to disable collision protection completely. (trunk r12397) svn path=/main/branches/2.1.6/; revision=12457 --- RELEASE-NOTES | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'RELEASE-NOTES') diff --git a/RELEASE-NOTES b/RELEASE-NOTES index 306951291..0ebeb7e03 100644 --- a/RELEASE-NOTES +++ b/RELEASE-NOTES @@ -12,7 +12,10 @@ portage-2.1.6 * File collision protection is now enabled by default via make.globals with FEATURES=protect-owned. In order to protect files from be overwritten or removed a inappropriate times, it is recommended to leave protect-owned - (or the similar collision-protect feature) enabled at all times. + (or the similar collision-protect feature) enabled at all times. If you + want to disable collision protection completely (not recommended), then + you need to ensure that neither protect-owned nor collision-protect are + enabled. * The python namespace for portage has been sanitized, all portage related code is now contained within the portage namespace. External script should be updated accordingly, though links exist for backward compability. -- cgit v1.2.3-1-g7c22