On Sun, 24 May 2009 20:54:14 +0200, Alan McKinnon wrote: > Portage will not let you unmerge portage or gcc without a fight. It > offers a way to back up these critical packages. No rational person > will attempt to argue that python in a *portage* system is not subject > to the same constraints.
Yes, and it used to warn you. > But it's not working that way today. Ergo, it is broken. The problem is that checking system is not enough, portage should also check that the package is not a dependency of anything in system. The problem with python is merely an example of what not checking this can do. For example, glibc could be taken out of system and replaced by a virtual that could be satisfied by glibc or eblic, but portage should still complain if you try to remove the only libc you have installed. -- Neil Bothwick The Borg Cable Co: The subscriber's wishes are irrelevant.
signature.asc
Description: PGP signature
