Q applets/en

The q applets are a collection of small and fast Portage helper tools written in C. This guide covers some common uses of these helper tools, which are provided through the package.

The package is a collection of very fast utilities written in C, which are meant to offer a faster but more limited alternative to their  counterparts. Please note that q applets are not meant to replace gentoolkit. The utilities may be much more efficient than the equivalent ones from gentoolkit and might be better suited to be used in scripts that need to call Portage repeatedly, but they do not offer the same functionality. q applets do not consider eclasses and do not provide tools like or.

Emerge
Install the q applets:

Configuration
Before using the applets first initialize the cache:

Invocation
The complete list of applications that are provided by can be listed by typing  or. 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.

To see the available applets with a short description of their function, use :

How to find a package to which a file belongs (qfile)
The command finds the package to which a file belongs:

Verifying package integrity (qcheck)
To check the MD5 sums or modification times of the files installed by some package, use the application:

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

Listing packages which depend on some package (qdepends)
Of course there's also an application which allows to list all the packages which depend on some package. This is done using. Use the  option to show all the DEPEND, RDEPEND , and PDEPEND information for a package.

Listing all packages (installed or not) which depend on some package (qgrep)
The q applets can be used to find ebuilds that mention an ebuild's name ("libechonest" is used in the example below) with great speed:

Listing files that belong to an ebuild (qlist)
The command gives a list of all files that belong to an ebuild.

Looking for packages that use some USE flag (quse)
Listing used USE flags is done with, which must be run with root permissions. It may take some time to first create/update the ebuild cache.

Finding package sizes (qsize)
To show the size of a package, use the application:

Searching the Portage tree (qsearch)
One of the most powerful tools of is. This tool allows to search the Portage tree much faster than using the command.

Here are some examples of its usage:

The homepage of packages can be queried using the  option:

In another example, let's look for a jabber client:

Extracting information from emerge logs (qlop)
There is also a tool that allows to extract useful information from the file. It is called and it can be useful when package compilation times need to be estimated or to compare build times with other systems. It also allows to check what's compiling at the moment and how long it will probably take - which is handy when working in the console and don't have any other means to check it.

To see how long a build usually takes:

To see what is emerging at the moment and how long the process has been running already: