Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Tue, 08 Apr 2008 11:51:29 +0200, Michael Schmarck wrote:
>
>> In "prose": I have kde-i18n-3.5.8 installed. In tree, there's
>> an update available (kde-i18n-3.5.9).
>>
>> Why was that updatedable package not picked up, when I ran
>> emerge -DuvatN world? I also tried "emerge -Duvat world" -
>> same effect.
>
> Is kde-i18n in your world file?
No, it's not.
> If emerge --depclean -p suggests removing
> it, it's not. Add it with emerge -n kde-i18n.
Hm - why should I want to add kde-i18n to the world file?
I ran "emerge -D" (--deep). From man emerge:
--deep (-D)
This flag forces emerge to consider the entire dependency tree
of packages, instead of checking only the immediate dependencies
of the packages. As an example, this catches updates in
libraries that are not directly listed in the dependencies of a
package. Also see --with-bdeps for behavior with respect to
build time dependencies that are not strictly required.
kde-i18n got installed as a dependency of some KDE package. Hmm...
I suppose I got it, because I used to have kde-meta installed. And
that package got "lost", somehow. And as it's no longer installed,
there's nothing installed on my system which has kde-i18n as a
dependency. And it's not in the world file.
As that's so, emerge "lost track" of this package, so to say.
Does that sound like a correct summary?
Connected question: How do I quickly find all the packages that
got installed as a dependency, but which are no longer needed,
because the dependent package got removed (as an example, I'd
like to find kde-i18n, because that used to be a dependency of
kde-meta and kde-meta is no longer installed).
Thanks,
Michael
--
gentoo-user@lists.gentoo.org mailing list
