Re: [gentoo-user] Question about eix-test-obsolete output

[Vaeth]

Dale wrote:
> Vaeth wrote:
> > > Is this not in portage, not in the world file or what?
> > >
> > > Installed packages with a version not in the database (or masked):
>
> Also, emerge -uvDNp comes out clean.  Nothing to upgrade or downgrade.
> Revdep-rebuild comes out clean as well.

The installed packages are not necessarily in a one-to-one correspondence
with emerge -NaDuv world.
More precisely, the following are the exceptions:

1. It might be that a package A was installed earlier as a dependency of
   another package B. If you then uninstalled that package B, or if you
   changed a useflags of package B, or if the ebuild author changed
   the dependencies for package B, it might be that package A is no
   longer needed. So emerge -NaDuv world will not see a reason to upgrade
   this package.

2. It might be a slotted package, and an old slot is not needed by
   anything.

Ideally, you should see both types listed for removal with
emerge -p --depclean

eix does not care *why* a package is installed. If you just list the 
package in question with eix, you will see which versions are installed 
and which versions are available in the database (i.e. in your case: 
available in the portage tree), and you will see that the installed 
version (or at least one of them) is not available anymore...

Usually this is a hint that you will want to upgrade that version or
uninstall it or that you want to keep a local copy of the original ebuild
in your overlay (and usually also of the tarball) (the latter only
for the case that you disagree with the gentoo developers and want to
continue to use the old version for some reason - you have to make sure
that you can still reemerge the package for the case that e.g.
revdep-rebuilds finds a missing library in that package).

Regards
Martin
-- 
gentoo-user@l.g.o mailing list