I just got hit hard by an autoclean following an emerge - lost about half my box because things it removed *were still needed, like sed, half of perl, etc.*. I checked my make.conf and I had not uncommented the AUTOCLEAN="yes" line, which means that the default behaviour is yes. This is a damaging features (as always, in my opinion) since it's effectiveness only seems to be marginal compared to the accidental damage it causes. Can the default behavior for autoclean be set back to NO?
from my emerge.log - as you see, i did an update on imagemagick, after which a whole slew of ebuilds were unmerged. After that unmerge, a few days pass, i go to emerge -u world and it fails twice (hence the two bottom entries). about the only info i can think to pass as I rebuild missing parts. === rsync Started emerge on: Nov 05, 2002 *** emerge search imagemagick Started emerge on: Nov 05, 2002 *** emerge clean <<< unmerge success: sys-kernel/linux-headers-2.4.18-r2 <<< unmerge success: sys-apps/supersed-3.58 <<< unmerge success: app-editors/nano-1.0.8-r1 <<< unmerge success: dev-libs/openssl-0.9.6e <<< unmerge success: dev-perl/MIME-Base64-2.12-r1 Started emerge on: Nov 06, 2002 *** emerge rsync === rsync Started emerge on: Nov 07, 2002 *** emerge rsync === rsync Started emerge on: Nov 08, 2002 *** emerge rsync === rsync Started emerge on: Nov 09, 2002 *** emerge rsync === rsync Started emerge on: Nov 09, 2002 *** emerge --update world >>> emerge (1 of 4) sys-apps/procps-2.0.10-r1 to / Started emerge on: Nov 09, 2002 *** emerge --update world >>> emerge (1 of 4) sys-apps/procps-2.0.10-r1 to /
The default behavior is yes because without it your symlinks for libs can be yanked wrongly. According to what you posted, you ran 'emerge clean'. Doesn't show anything helpful. If you're complaining about supersed killing sed, then that's the complaint, as it _should_ coexist nicely, even when unmerged.
