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