Source Repository:Repository:Gentoo Portage Tree

Summary: A command to search and query ebuilds, portage including local settings, overlays, version changes, and more.

Use Flags

Build with upstream's CXXFLAGS/LDFLAGS for debugging support; not recommended for normal use.
Make DEP=true the default which enables support for {,R,P}DEPEND but requires roughly double disk and memory.
Create description of the eix cache file additionally in html format
Accept upstream's choices for CXXFLAGS/LDFLAGS for optimization. Absense of this USE flag does not strip user's *FLAGS
Make REQUIRED_USE=true the default which enables support for REQUIRED_USE but requires more disk and memory.
This adds some checks which can prevent certain exploits if e.g. the eix code has a bug. If you use the hardened toolchain, using this flag does not increase security and can even lead to problems.
Adds several more agressive CXXFLAGS/LDFLAGS for optimization like graphite (if available). May cause trouble with some buggy compiler versions. Absense of this USE flag does not strip user's *FLAGS
Add many checks to prevent exploits if eix code has a bug. This will slow down eix considerably. Use only if you are paranoid or have reasons to suspect a bug.
Compile in support for portage's sqlite backend; to actually use it you need additional configuration of portage and eix
Swap role of remote addresses in eix-remote, making the data from gpo.zugaina.org the first choice.
Create separate binary for script helper tools; useful if they are called extremely often



Xorg and other Updates

Xorg and other Updates
2017-02-05 by Oleg

Kde4 to Plasma5 migration

Migration to Plasma 5
2017-02-02 by Oleg

Funtoo Services available thru BreezyOps

Funtoo Linux support and consulting services are now available from BreezyOps.
2017-01-30 by Drobbins



We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.


To install eix, emerge it:

# emerge eix


To include your layman repositories for synchronization:

# echo "*" >> /etc/eix-sync.conf

Update eix by running:

# eix-update


The basic usage of eix is simply using its name as a prefix to the package you are looking for:

# eix foo

This will give you a fairly verbose list of packages containing the term 'foo' in their name. It gives you information about which versions are available, whether they are stable, current or live, a description of the package and a list of the USE flags for all the packages combined - sometimes different versions of packages have different USE flags so you may need to check which a specific package contains with equery.

More detailed example

Suppose that you are interested in learning about the various available kernels in Portage. Eix can help with that. By running the following command, you will find the answer that you are looking for:

# eix -# sys-kernel/

To receive more information in the output, add the -c argument when you run eix:

# eix -c sys-kernel/

Showing what you have installed

A handy feature of eix is the ability to quickly show you which packages you have installed on your system.

# eix-installed all

This will output all the packages you have explicitly installed along with the version number. There are other options to get more specific information with this command so check the man page for details.

This can be handy for when you do backups of your system, the list could be sent to a file before you run rsync:

# eix-installed all > ~/installed_list.txt

Searching other overlays

It is possible search in more than just the main portage tree and your local overlay. By using the eix-remote command you can configure eix to load, update and search multiple external overlays.

To add the list of external overlays to eix:

# eix-remote update 
# eix-sync

Now you are ready to search for packages inside the main funtoo portage tree and in all the third party overlays by using the -R argument:

# eix -R foo
This is will give you a list of all the packages and versions, as well as telling you which overlay they belong to. Once you have found something you want to emerge you can add the overlay, with either

# layman -a [overlay_name]

or by using eix-layman, and then just emerge the package in the normal way.