On Tue, 18 Jan 2005 19:27:42 +0000 Stuart Herbert <[EMAIL PROTECTED]> wrote: | At the moment, the problem with any meta-package is uninstalling it. | emerge -C kde-3.2 doesn't remove KDE 3.2. Portage removes the | meta-package itself, but none of the kdebase, kdelibs etc that the | meta-package installed. Administrators have to go around and emerge | -C the individual packages. | | That's fine with the monolithic ebuilds. But having to do this for | 400+ ebuilds is unreasonable. It's a lot of work to do, and there's a | significant risk of human error. | | Until stable Portage has the support for auto-uninstalling all these | packages, I believe we shouldn't mark the split packages as stable on | any arch.
emerge -C kde-meta && emerge depclean Works fine, so long as you haven't ever done emerge /path/to/ebuild or installed packages which have conditional code based upon what the user has installed on their system (generally indicated by the has_version in global scope QA notice). -- Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgpeiFgYGOsYm.pgp
Description: PGP signature
