| 1 |
Molle Bestefich wrote: |
| 2 |
> I think a piece might be missing from Portage. |
| 3 |
> |
| 4 |
> I'll depict my workflow as an example. |
| 5 |
|
| 6 |
Same thing with a package called 'seamonkey': |
| 7 |
|
| 8 |
# emerge -Dpt world |
| 9 |
These are the packages that would be merged, in reverse order: |
| 10 |
Calculating world dependencies... done! |
| 11 |
[blocks B ] www-client/seamonkey (is blocking www-client/mozilla-1.7.13) |
| 12 |
[blocks B ] >=sys-apps/shadow-4.0.14-r2 (is blocking |
| 13 |
sys-apps/pam-login-4.0.14) |
| 14 |
[blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2) |
| 15 |
... etc ... |
| 16 |
|
| 17 |
# emerge --unmerge seamonkey |
| 18 |
--- Couldn't find 'seamonkey' to unmerge. |
| 19 |
>>> No packages selected for removal by unmerge. |
| 20 |
|
| 21 |
# equery d seamonkey |
| 22 |
[ Searching for packages depending on seamonkey... ] |
| 23 |
|
| 24 |
# |
| 25 |
|
| 26 |
Nobody wants a seamonkey, and I haven't got one already, but Portage |
| 27 |
wants to smuggle one in anyway if I tell it to upgrade world. |
| 28 |
|
| 29 |
Where's the piece that can tell me why Portage wants to do so? |
| 30 |
|
| 31 |
(Alternatively, what's the manual process to find out?) |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives