On 07/28/2013 05:39 PM, Duncan wrote: > I haven't checked the details and depclean does run far faster than > revdep-rebuild so whatever it's doing isn't as thorough, but depclean now > does at least some actual on-system checking before removing a package, > and will refuse to remove a package it otherwise would (no database deps > requiring it so the database says it's fine to remove) with an > explanation of what's actually linked against it, if depclean's pre-clean > scans indicate that removing the package would otherwise leave an > unsatisfied/dangling linkage, asking you to rebuild the depending package > first to remove that in-practice-but-not-in-database dependency.
This behavior is controlled by the --depclean-lib-check option and also interacts with FEATURES=preserve-libs. I suspect that the majority of people have FEATURES=preserve-libs enabled these days, and for them the behavior is for depclean to remove the packages but preserve their libraries as needed (it's documented in the --depclean-lib-check section of the emerge man page). -- Thanks, Zac
