On Tue, 20 Feb 2007 09:42:13 +0200, Alan McKinnon wrote: > 1. It's an orphan, left over from an unmerge that wasn't fully > successful. if you don't need them, delete them. > 2. A package was installed, and it created it's own binaries for it's > own use. Portage didn't put them there so doesn't know about them. This > is rare and usually applies to config and other data files. In this > case it's up to you to figure out what the file is as portage can't > help. > 3. You compiled something long ago by hand and didn't put it > in /usr/local/ like you were supposed to, and used /usr/ instead. In > this case you get to remember what you did by yourself :-)
4. The file was installed by portage and subsequently modified. When you uninstalled the package, portage didn't remove this file because the mtime differed from what it had installed. This typically occurs with .la files (Mark's revdep-rebuild output showed some of these) after fix_libtool_files.sh has changed them. -- Neil Bothwick Top Oxymorons Number 11: Terribly pleased
signature.asc
Description: PGP signature
