| 1 |
On Mon, 4 May 2009 13:11:02 +0100 |
| 2 |
Matt Causey <matt.causey@×××××.com> wrote: |
| 3 |
|
| 4 |
--snip-- |
| 5 |
|
| 6 |
> |
| 7 |
> Along the same lines, how does the ebuild know what to remove on |
| 8 |
> --unmerge? For example I'm wandering around and looking at ebuilds: |
| 9 |
> |
| 10 |
> prometheus ethtool # pwd |
| 11 |
> /usr/portage/sys-apps/ethtool |
| 12 |
> prometheus ethtool # ls |
| 13 |
> ChangeLog Manifest ethtool-6.ebuild metadata.xml |
| 14 |
> prometheus ethtool # |
| 15 |
> |
| 16 |
> I see nothing in that ebuild which describes the files that ethtool |
| 17 |
> put on the system. Yet an --unmerge removes the binaries and |
| 18 |
> source....interesting. |
| 19 |
> |
| 20 |
> So I found a CONTENTS file: |
| 21 |
> |
| 22 |
> prometheus ethtool-6 # pwd |
| 23 |
> /var/db/pkg/sys-apps/ethtool-6 |
| 24 |
> prometheus ethtool-6 # cat CONTENTS |
| 25 |
> dir /usr |
| 26 |
> dir /usr/sbin |
| 27 |
|
| 28 |
--snip-- |
| 29 |
|
| 30 |
|
| 31 |
Another way to check which files are installed by a given package |
| 32 |
and to which package a given file belongs. |
| 33 |
|
| 34 |
emerge app-portage/portage-utils (if you haven't already) |
| 35 |
|
| 36 |
Example: |
| 37 |
|
| 38 |
~ $ qlist ethtool |
| 39 |
/usr/share/man/man8/ethtool.8.bz2 |
| 40 |
/usr/share/doc/ethtool-6/AUTHORS.bz2 |
| 41 |
/usr/share/doc/ethtool-6/ChangeLog.bz2 |
| 42 |
/usr/share/doc/ethtool-6/NEWS.bz2 |
| 43 |
/usr/share/doc/ethtool-6/README.bz2 |
| 44 |
/usr/sbin/ethtool |
| 45 |
~ $ |
| 46 |
|
| 47 |
~ $ qfile ethtool |
| 48 |
sys-apps/ethtool (/usr/sbin/ethtool) |
| 49 |
~ $ |
| 50 |
|
| 51 |
~ $ qlist nvidia-drivers | grep /lib/modules |
| 52 |
/lib/modules/2.6.28-core2/video/nvidia.ko |
| 53 |
~ $ |
| 54 |
|
| 55 |
HTH |
| 56 |
|
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
Best regards, |
| 61 |
Daniel |
Archives