No contents found at URL
Current Maintainer(s):Antoine Pinsard
Source Repository:Repository:Gentoo Portage Tree

Summary: A USE flags manager



Perl Update

Perl Update and Kernel Update.
2016-10-22 by Oleg

ZFS Status Update

ZFS Status Update
2016-10-18 by Oleg

Selinux Support

Selinux Support
2016-09-20 by Oleg



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.

Chuse stands for CHange USE. This is a Portage tool for managing your local USE flags (ie. set within /etc/portage/package.use).

In contrast to its several equivalents, it is designed with a very specific goal: Make your /etc/portage/package.use management easier. This means chuse does not handle other package.* and focuses on package.use.


Chuse is available from the sapher overlay.

Once you have added this overlay through layman or whatever, just emerge chuse.

# emerge -av chuse
By default, chuse uses the following hierarchy pattern: /etc/portage/package.use/<cat-name>/<pkg-name>

This file would contain each rules for the package <pkg-name> in the category <cat-name>.

If you don't use this hierarchy pattern

If you want to use your own current pattern

You can change this pattern by explicitely setting the PACKAGE_USE_FILE_PATTERN environment variable (eg. in your bashrc).

~/.bashrc - PACKAGE_USE_FILE_PATTERN examples
PACKAGE_USE_FILE_PATTERN="/etc/portage/package.use" # All in one file
PACKAGE_USE_FILE_PATTERN="/etc/portage/package.use/%(cat)s" # One file per category
PACKAGE_USE_FILE_PATTERN="/etc/portage/package.use/%(cat)s/%(pkg)s" # This is the default
PACKAGE_USE_FILE_PATTERN="/etc/portage/package.use/chuse" # One file dedicated to chuse

%(cat)s and %(pkg)s would be respectively replaced by the category name and the package name of the atom you want to alter USE flags.

If you want to adopt this hierarchy pattern

You will have to backup your current USE flags in a file and reorganize the package.use hierarchy. To achieve this, issue the following commands:

# chuse --dump > /root/package.use.bak # Concat all your rules in one file
# chuse --load /root/package.use.bak # Parse the file to organize your package.use
To avoid mistakes, chuse --load will ask you before erasing /etc/portage/package.use.


   chuse <atom> [[modifier]<flag> ...] [(--because|#) <reason>]
       Obviously 'version-selector' and 'version' should never be set without the other.
       One of : "=", ">", "<", ">=", "<=".
       An ebuild category (validity won't be checked).
       An ebuild package (validity won't be checked).
       A version of the underlying package (validity won't be checked).
       A slot of the underlying package (validity won't be checked.
       One of : "+", "-", "%" (% means reset default). If omitted, "+" is assumed.
       A USE flag (validity won't be checked).
       The reason why you changed these USE flags (so that you remember why you set this and if now
       you can reset default for instance).

If no flag is specified, this will display the current rules matching the underlying atom.


Show the flags you altered for firefox:

$ chuse www-client/firefox
Add system-cairo, remove system-icu and reset system-jpeg for firefox >= 37.0.1:

# chuse ">=www-client/firefox-37.0.1" system-cairo -system-icu %system-jpeg