Bug 1358 – Unmerge packages that depend on a package that is being removed

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Shahar Goldin 2002-03-27 00:30:03 UTC]

emerge --unmerge kde-libs
for example
should unmerge anything that depends on kde-libs
like, kde-base and koffice and so on

this is in the far future and non-critical and stuff

[Comment 1 Leif Brown 2002-05-01 09:28:42 UTC]

Seems like this would conflict with USE "-XXX" functionality, and the cleaning
of false dependencies.  (kde depends on kdetoys, for instance.)

Even worse, if a package listed a false dependency in some versions but not others.

And packages with joint ownership of files...

Maybe a shade of gray between "dependent" and "independant" -- an "optional" tag?

[Comment 2 Shahar Goldin 2002-05-02 12:26:45 UTC]

hmm
KDE is a special case since it isn't really an ebuild, it just calls all the 
kde components in the right order, if I recall correctly.
unmergeing kde should remove all the components that emerge kde installed

[Comment 3 Arne Brix 2002-09-29 08:52:55 UTC]

this would really be a nice feature. it could be even better together with automatic updating of packages, whose usevars have changed and packages which are not in world as well as removal of packages which are not needed anymore  ideally after an  emerge -u world --apply-all-changes-or-something  your packages would be the same as if you would have done reinstall with your current configuration. it would be a bit like  emerge -eu world together whith removal of unneeded packages, but much much faster, doing no unneccessary work. 

[Comment 4 Nicholas Jones (RETIRED) 2002-10-22 22:57:06 UTC]

emerge depclean
does this... >= portage-2.0.41

[Comment 5 niecheng 2009-12-18 01:24:49 UTC]

(In reply to comment #4)
> emerge depclean
> does this... >= portage-2.0.41