Molle Bestefich wrote:
I think a piece might be missing from Portage.
I'll depict my workflow as an example.
Same thing with a package called 'seamonkey':
# emerge -Dpt world
These are the packages that would be merged, in reverse order:
Calculating world dependencies... done!
[blocks B ] www-client/seamonkey (is blocking www-client/mozilla-1.7.13)
[blocks B ] >=sys-apps/shadow-4.0.14-r2 (is blocking
sys-apps/pam-login-4.0.14)
[blocks B ] sys-apps/pam-login (is blocking sys-apps/shadow-4.0.15-r2)
... etc ...
# emerge --unmerge seamonkey
--- Couldn't find 'seamonkey' to unmerge.
No packages selected for removal by unmerge.
# equery d seamonkey
[ Searching for packages depending on seamonkey... ]
#
Nobody wants a seamonkey, and I haven't got one already, but Portage
wants to smuggle one in anyway if I tell it to upgrade world.
Where's the piece that can tell me why Portage wants to do so?
(Alternatively, what's the manual process to find out?)
--
[email protected] mailing list
