Language Selection

English French German Italian Portuguese Spanish

Gentoo Portage secrets

Filed under
Gentoo
HowTos

Gentoo Linux is perhaps the most-used source-based Linux distribution. One secret to its success is the powerful and handy Portage package management system. While Gentoo comes with extensive documentation covering most aspects of using Portage, the techniques described in Gentoo's handbook and other documentation are not always the most effective ones. Here are some insider tips that can greatly increase your productivity.

Search faster

Before you install a package, you usually look for it via Portage's search capabilities. Portage's emerge utility has --search and --searchdesc options, but using them is not enjoyable, because they take a long time to run. That's why we've seen the emergence of third-party search front ends for Portage, such as esearch and eix. Their common idea is to use their own search indexes to speed up searches. When using either utility, you have to rebuild the index after updating the Portage tree, and after installing and uninstalling software.

Of the two, eix works faster and has more capabilities. You can get information on the utility from its man page or by invoking eix --help. To use eix to search for a package whose name contains foo, simply invoke eix foo.

Eix is a very flexible tool. It can give you more information on packages than esearch or emerge -s. It can search through different fields (e.g. package name, category, or description), it can search for regular expressions or wildcard patterns, or do fuzzy searches, and its output can be configured for use in scripts.

Optimizing traffic usage

Full Story.

Great read

I never knew about esearch or eix, but after using them I know they will always be on my system. At least 3x faster than a simple emerge -s.

re: Great read

Yeah it is. I've used some of them before when I saw them mentioned in the forums, but I couldn't remember them too much longer. I still end up using emerge -s. Blushing

I'm gonna make me a cheat sheet this time! Big Grin

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Brocade Wants to Be Red Hat of OpenDaylight

Brocade wants to have the same relationship with OpenDaylight as Red Hat has with Linux. Read more

Rise of Linux – a hacker’s history

The original code of Linux was written for fun, or in Eric Raymond’s phrase, to ‘scratch the itch’ of Linus Torvalds, and later to satisfy the enthusiasm and programming itch of an assortment of hackers and hobbyists who, for the most part, had grown up in the age of the ZX80 and the BBC Micro, Acorns and Apricots, for which the code was often available – and hackable. For those who spent their childhood or adolescence delving into the home computers of the late Seventies and early Eighties, playing with software was a learning experience, and something to be shared. Linux could be said to have grown out of this ethos as much as it grew out of the free software movement, or the early Nineties culture of Usenet where “if you wrote something neat you posted it to Usenet” and the only proviso that came with the software was that “if the software breaks you get to keep both pieces.” Read more

Lollipop unwrapped: Chromium WebView will update via Google Play

Android 5.0, codenamed Lollipop, has introduced a key change to the WebView component, used by app developers to display HTML 5 content within their apps, making new features more readily available. Read more

Being a Sporadic Overview Of Linux Distribution Release Validation Processes

Our glorious Fedora uses Mediawiki to manage both test cases and test results for manual release validation. This is clearly ludicrous, but works much better than it has any right to. ‘Dress rehearsal’ composes of the entire release media set are built and denoted as Test Composes or Release Candidates, which can be treated interchangably as ‘composes’ for our purposes here. Each compose represents a test event. In the ‘TCMS’ a test event is represented as a set of wiki pages; each wiki page can be referred to as a test type. Each wiki page must contain at least one wiki table with the rows representing a concept I refer to as a unique test or a test instance. There may be multiple tables on a page; usually they will be in separate wiki page sections. Read more