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