On Fri, Jun 26, 2009 at 7:24 PM, Steve Herber<her...@thing.com> wrote:
> I removed a package recently and portage keeps wanting to put it back
> into the system. How can I find out why portage wants to reinstall it?
> Here is a cleaned up example:
>
> emerge --ask --verbose --deep --update world
>
> Calculating dependencies... done!
> [ebuild N ] media-video/vcdimager-0.7.23 USE="-minimal -xml" 986 kB
> [ebuild U ] dev-lang/php-5.2.10 [5.2.9-r2]
> [ebuild U ] net-libs/xulrunner-1.9.0.11 [1.9.0.10]
> [ebuild U ] www-client/mozilla-firefox-3.0.11 [3.0.10]
> [ebuild U ] sys-fs/udev-141 [124-r2]
> [ebuild U ] sys-fs/cryptsetup-1.0.6-r2 [1.0.5-r1]
> [blocks b ] >=sys-fs/udev-126 (">=sys-fs/udev-126" is blocking
> sys-fs/cryptsetup-1.0.5-r1)
>
> Total: 6 packages (5 upgrades, 1 new), Size of downloads: 55,215 kB
> Conflict: 1 block
>
> How can I find the package that keeps pulling in vcdimager?
>
> Thanks,
>
> --
> Steve Herber her...@thing.com work: 206-221-7262
> Software Engineer, UW Medicine, IT Services home: 425-454-2399
>
>
As Joe says emerge --tree is the most typical answer for this.
Another good one is equery depends vcdimager as it attempts to show
what use flags might have called the package in.
Hope this helps,
Mark
