From: Daniel Iliev <daniel.iliev@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Removing Packages with Portage
Date: Mon, 4 May 2009 18:11:48 +0300 [thread overview]
Message-ID: <20090504181148.7e402d6e@ilievnet.com> (raw)
In-Reply-To: <ac71f2bb0905040511x701e665cxcd8997b62862087a@mail.gmail.com>
On Mon, 4 May 2009 13:11:02 +0100
Matt Causey <matt.causey@gmail.com> wrote:
--snip--
>
> Along the same lines, how does the ebuild know what to remove on
> --unmerge? For example I'm wandering around and looking at ebuilds:
>
> prometheus ethtool # pwd
> /usr/portage/sys-apps/ethtool
> prometheus ethtool # ls
> ChangeLog Manifest ethtool-6.ebuild metadata.xml
> prometheus ethtool #
>
> I see nothing in that ebuild which describes the files that ethtool
> put on the system. Yet an --unmerge removes the binaries and
> source....interesting.
>
> So I found a CONTENTS file:
>
> prometheus ethtool-6 # pwd
> /var/db/pkg/sys-apps/ethtool-6
> prometheus ethtool-6 # cat CONTENTS
> dir /usr
> dir /usr/sbin
--snip--
Another way to check which files are installed by a given package
and to which package a given file belongs.
emerge app-portage/portage-utils (if you haven't already)
Example:
~ $ qlist ethtool
/usr/share/man/man8/ethtool.8.bz2
/usr/share/doc/ethtool-6/AUTHORS.bz2
/usr/share/doc/ethtool-6/ChangeLog.bz2
/usr/share/doc/ethtool-6/NEWS.bz2
/usr/share/doc/ethtool-6/README.bz2
/usr/sbin/ethtool
~ $
~ $ qfile ethtool
sys-apps/ethtool (/usr/sbin/ethtool)
~ $
~ $ qlist nvidia-drivers | grep /lib/modules
/lib/modules/2.6.28-core2/video/nvidia.ko
~ $
HTH
--
Best regards,
Daniel
prev parent reply other threads:[~2009-05-04 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 9:45 [gentoo-user] Removing Packages with Portage Matt Causey
2009-05-04 9:55 ` Neil Bothwick
2009-05-04 11:14 ` KH
2009-05-04 11:08 ` Alan McKinnon
2009-05-04 12:11 ` Matt Causey
2009-05-04 14:54 ` Alan McKinnon
2009-05-04 15:11 ` Daniel Iliev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090504181148.7e402d6e@ilievnet.com \
--to=daniel.iliev@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox