[gentoo-user] What's pulling these ebuilds in?

[gentoo-user] What's pulling these ebuilds in?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

Hi All,

I went to update my laptop today and after it finished (by which time I had 
almost woken up) I realised that it had emerged two gnome-base components 
(this is a KDE only build with all the -gnome -gtk USE flags already set as 
required);
======================================================
1152880704: Started emerge on: Jul 14, 2006 13:38:24
1152880704:  *** emerge --update --fetchonly --deep --verbose world
1152880714:  >>> emerge (1 of 15) dev-util/intltool-0.35.0 to /
1152880717:  >>> emerge (2 of 15) media-libs/fontconfig-2.3.2-r1 to /
1152880726:  >>> emerge (3 of 15) app-text/poppler-0.5.3 to /
1152880736:  >>> emerge (4 of 15) dev-libs/glib-2.10.3 to /
1152880762:  >>> emerge (5 of 15) dev-libs/libxml2-2.6.26 to /
1152880793:  >>> emerge (6 of 15) dev-libs/libxslt-1.1.17 to /
1152880811:  >>> emerge (7 of 15) x11-libs/pango-1.12.3 to /
1152880823:  >>> emerge (8 of 15) dev-libs/atk-1.11.4 to /
1152880829:  >>> emerge (9 of 15) x11-libs/gtk+-2.8.19 to /
1152880940:  >>> emerge (10 of 15) media-libs/libwmf-0.2.8.3-r1 to /
1152880957:  >>> emerge (11 of 15) media-gfx/imagemagick-6.2.8.0 to /
1152881004:  >>> emerge (12 of 15) media-libs/libdvdread-0.9.4-r1 to /
1152881008:  >>> emerge (13 of 15) gnome-base/orbit-2.14.0 to /
1152881016:  >>> emerge (14 of 15) gnome-base/gconf-2.14.0 to /
1152881034:  >>> emerge (15 of 15) app-text/poppler-bindings-0.5.3 to /
1152881034:  *** Finished. Cleaning up...
1152881034:  *** terminating.
======================================================

Is there a way of finding out what pulled them in *after* they have been 
installed (I am looking for something like a retrospective emerge -t option)?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] What's pulling these ebuilds in?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]

On Fri, 14 Jul 2006 16:32:45 +0100, Mick wrote:

> Is there a way of finding out what pulled them in *after* they have
> been installed (I am looking for something like a retrospective emerge
> -t option)?

"equery depends packagename" should give you a clue.


-- 
Neil Bothwick

An example of hard water is ice.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] What's pulling these ebuilds in?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

On Friday 14 July 2006 18:04, Neil Bothwick wrote:
> On Fri, 14 Jul 2006 16:32:45 +0100, Mick wrote:
> > Is there a way of finding out what pulled them in *after* they have
> > been installed (I am looking for something like a retrospective emerge
> > -t option)?
>
> "equery depends packagename" should give you a clue.

Thanks!  It seems that:
=================================
# equery depends orbit
[ Searching for packages depending on orbit... ]
gnome-base/gconf-2.14.0

# equery depends gconf
[ Searching for packages depending on gconf... ]
media-libs/gst-plugins-0.8.11

# equery depends gst-plugins
[ Searching for packages depending on gst-plugins... ]
#
=================================

That said, my gst-plugin has all the right flags set:  
[ebuild   R   ] media-libs/gst-plugins-0.8.11  USE="alsa oss -debug -esd"

This must be a new dependency then?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]