| 1 |
Daniel Iliev wrote: |
| 2 |
|
| 3 |
> I have no problem with the redundant cruft - when I want just to try |
| 4 |
> some package I do "emerge --pretend" and record the list of dependencies |
| 5 |
> it wants to pull-in. If I decide the package is not useful to me, I |
| 6 |
> "un-emerge" not only the package, but also the dependencies it had |
| 7 |
> pulled-in during its installation. |
| 8 |
|
| 9 |
That's risky! |
| 10 |
|
| 11 |
Suppose, you want to install "a". "a" needs "b". You keep "a" & "b" |
| 12 |
installed. |
| 13 |
|
| 14 |
Later on, you decide to try "c". "c" needs "b" as well. But as "b" |
| 15 |
is already installed, "emerge -p c" won't show "b". You install "c" |
| 16 |
and do *NOT* write down, that "c" needs "b", as you don't know that. |
| 17 |
|
| 18 |
Even more later on, you decide to deinstall "a". According to what |
| 19 |
you wrote above and according to your documentation, you'll see that |
| 20 |
"b" got installed because of "a" and you'll remove "b" as well. |
| 21 |
|
| 22 |
Yet more later on, you find out, that "c" is broken and wonder why. |
| 23 |
|
| 24 |
The basic problem here is, that there's no way to see, which packages |
| 25 |
depend on a given package - at least I don't know how to find that out. |
| 26 |
What's required, is a way to be told, that packages "a" and "c" depend |
| 27 |
on "b". |
| 28 |
|
| 29 |
Now, if you'd use the world file as it was supposed to be used, you'd |
| 30 |
remove "a" and could do a "emerge --depclean --pretend". Doing so, the |
| 31 |
system would *NOT* show you package "b", as it's still a dependency |
| 32 |
of "c". Only after you remove "c" as well, "b" would show up in a |
| 33 |
depclean run. |
| 34 |
|
| 35 |
Alexander Skwar |
| 36 |
-- |
| 37 |
The more laws and order are made prominent, the more thieves and |
| 38 |
robbers there will be. |
| 39 |
-- Lao Tsu |
| 40 |
-- |
| 41 |
gentoo-user@g.o mailing list |
Archives