nightmorph    06/04/30 18:45:10

  Added:                portage-utils.xml
  Log:
  rane's brand spanking new portage-utils doc is now here, closes bug 123327

Revision  Changes    Path
1.1                  xml/htdocs/doc/en/portage-utils.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/portage-utils.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/portage-utils.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: portage-utils.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/portage-utils.xml,v 1.1 
2006/04/30 18:45:09 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">

<guide link="/doc/en/portage-utils.xml">

<title>Portage-utils</title>

<author title="Author">
  <mail link="[EMAIL PROTECTED]">Łukasz Damentko</mail>
</author>
<author title="Editor">
  <mail link="[EMAIL PROTECTED]">Joshua Saddler</mail>
</author>
<author title="Editor">
  <mail link="[EMAIL PROTECTED]">Marcelo Góes</mail>
</author>

<abstract>
This guide covers some common uses if portage-utils, a set of fast Portage
helper applications written in C.
</abstract>

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>

<version>1.0</version>
<date>2006-04-30</date>

<chapter>
<title>Introduction</title>
<section>
<body>

<p>
<c>portage-utils</c> is a collection of very fast utilities written in C, which
are meant to replace their counterparts included in <c>gentoolkit</c>. Although
<c>portage-utils</c> is not yet capable of fully replacing <c>gentoolkit</c>,
its utilities are much more efficient than the equivalent ones from
<c>gentoolkit</c>.
</p>

<p>
The removal of <c>gentoolkit</c> in favor of <c>portage-utils</c> is
discouraged, as <c>gentoolkit</c> contains some functions not implemented in
<c>portage-utils</c> yet, like <c>revdep-rebuild</c> and <c>glsa-check</c>.
Instead, you may want to consider having them both installed.
</p>

<p>
More information about <c>gentoolkit</c> can be found in the <uri
link="/doc/en/gentoolkit.xml">Gentoolkit</uri> guide.
</p>

<p>
You can view the complete list of applications in <c>portage-utils</c> by typing
<c>man q</c> or <c>q --help</c>. Please read the man page for each utility
described, as this guide is only meant to be a short reference for the most
useful functions and does not include all the information about each
application.
</p>

<p>
The first step of using <c>portage-utils</c> is to install the package:
</p>

<pre caption="Installing portage-utils">
# <i>emerge portage-utils</i>
</pre>

</body>
</section>
</chapter>

<chapter>
<title>Usage</title>
<section>
<title>How to find a package to which a file belongs</title>
<body>

<p>
<c>qfile</c> finds the package to which a file belongs:
</p>

<pre caption="Finding the package to which a file belongs">
$ <i>qfile /etc/fonts/fonts.conf</i>
media-libs/fontconfig (/etc/fonts/fonts.conf)
$ <i>qfile /usr/share/keymaps/atari/atari-uk-falcon.map.gz</i>
sys-apps/kbd (/usr/share/keymaps/atari/atari-uk-falcon.map.gz)
</pre>

</body>
</section>
<section>
<title>Verifying package integrity</title>
<body>

<p>
If you want to check MD5 sums or mtimes of the files installed by some package,
you can do it using the <c>qcheck</c> application:
</p>

<pre caption="Checking package integrity">
$ <i>qcheck portage-utils</i>
Checking app-portage/portage-utils-0.1.13 ...
  * 36 out of 36 files are good
</pre>

<p>
Of course, all the files which were changed after installation will be reported
here. If the application reports configuration files which you have manually
edited after installation, there's nothing to worry about.
</p>

</body>
</section>
<section>
<title>Listing packages which depend on some package</title>
<body>

<p>
Of course there's also an application which allows you to list all the packages
which depend on some package. This is done using <c>qdepends</c>.  Use the
<c>-a</c> flag to show all the DEPEND, RDEPEND, and PDEPEND information for a
package.
</p>

<pre caption="Listing packages which depend on some package">
$ <i>qdepends -a pygtk</i>
 * DEPEND
dev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0
&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0
&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric
virtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99
&gt;=dev-util/pkgconfig-0.9 sys-devel/patch
 * RDEPEND
dev-python/pygtk-2.8.2: &gt;=dev-lang/python-2.3 &gt;=x11-libs/gtk+-2.8.0
&gt;=dev-libs/glib-2.8.0 &gt;=x11-libs/pango-1.10.0 &gt;=dev-libs/atk-1.8.0
&gt;=gnome-base/libglade-2.5.0 &gt;=dev-python/pycairo-0.9.0 dev-python/numeric
virtual/opengl dev-python/pyopengl &gt;=x11-libs/gtkglarea-1.99
 * PDEPEND
</pre>

</body>
</section>
<section>
<title>Listing files that belong to an ebuild</title>
<body>

<p>
<c>qlist</c> gives you a list of all files that belong to an ebuild.
</p>

<pre caption="Listing files which belong to an ebuild file">
$ <i>qlist vim</i>
/usr/bin/gvim
/usr/bin/gvimdiff
/usr/bin/evim
/usr/bin/eview
/usr/bin/gview
/usr/bin/rgvim
[...]
</pre>

</body>
</section>
<section>
<title>Looking for packages that use some USE flag</title>
<body>

<p>
This is done with <c>quse</c>, which must be run as root. It may take some time
to first create/update the ebuild cache.
</p>

<pre caption="Looking for packages with the 'firefox' USE flag">
# <i>quse firefox</i>
app-office/openoffice/openoffice-2.0.2_rc1.ebuild binfilter curl eds firefox 
gnome gtk java kde ldap mozilla xml2 
dev-haskell/gtk2hs/gtk2hs-0.9.10.ebuild doc glade gnome mozilla firefox 
dev-java/swt/swt-3.1-r1.ebuild accessibility cairo firefox gnome mozilla 
[...]
</pre>

</body>
</section>
<section>
<title>Finding package sizes</title>
<body>

<p>
This is done with <c>qsize</c> application and is as simple as:
</p>

<pre caption="Finding package size">
$ <i>qsize vim</i>
app-editors/gvim-6.4: 10 files, 7 non-files, 2327.516 KB
app-editors/vim-6.4: 6 files, 2 non-files, 2058.14 KB
app-editors/vim-core-6.4: 1024 files, 68 non-files, 10950.984 KB
[...]
</pre>

</body>
</section>
</chapter>
</guide>



-- 
[email protected] mailing list

Reply via email to