Running Moksha under Sabayon

4 November 2015 HOWTOs, Installation guides, Overviews No comments

Moksha running under Sabayon

Moksha (theme: Moksha Radiance, wallpaper: 1366×768 calculate-dm 15) running under Sabayon

Moksha (pronounced: MOK-sha) is a free fork of Enlightenment 17 (E17), that is the default desktop environment of the lightweight Ubuntu (LTS) derivative, Bodhi Linux (BL). Its development began in 2015, when dissatisfied by the high resource usage and loss of features of the later Enlightenment releases, E18 and E19, Jeff Hoogland, the lead developer of Bodhi Linux, decided to fork E17 for BL.1 E19, for example, uses more RAM than LXDE even though E17 and Moksha use less RAM than LXDE and all other complete desktop environments that I am aware of (see Desktop environments and Sabayon for details). Its first stable release (version 0.1.0) was made on the 7th of August 2015.

While Moksha is pre-installed on later Bodhi Linux releases, it is not yet available as an official binary package, ebuild or PKGBUILD for any other Linux distribution, which means, of course, that if you wish to install it on other distributions you are left with really just one option: to compile it manually from source code and then install it yourself. Although, I have successfully made my own PKGBUILD for e_dbus-1.7.10 and moksha-0.1.0 and they can be found here. I have also (unsuccessfully) attempted to create an ebuild for Moksha, which can be found here, see it keeps giving me access violation errors related to /usr/bin/efreetd trying to create a directory /run/user/1000/.ecore. If you are interested in helping me fix this problem, feel free to start a pull request at GitHub. Fortunately, Jeff Hoogland along with other members of the Bodhi Linux community, are more than willing to help users of other distributions install and then customize Moksha to their liking, they even have their own forum specifically for such questions.

This blog post will walk you through the process of installing Moksha, getting it ready for easy use, getting modules you want and otherwise customizing it to your liking.


The following script should install Moksha for you, simply copy it into a shell script called “moksha.sh” (the name does not really matter, you could alternatively download moksha.sh from my GitHub repository), make it executable (run user $  chmod +x moksha.sh) and then run it with ./moksha.sh. This script is specifically designed to install Moksha on a freshly-installed Sabayon Spinbase machine, which is why its dependency-installing lines are so long. It is also worthwhile noting that this script uses the minimum of bandwidth to get the source code, because alternatively, if bandwidth is not a limitation, the wget lines (line #4-5) can be replaced with


of all the steps in this script, the running of ./autogen.sh --prefix=/usr is probably the most likely to return errors, which are usually related to missing dependencies. If you get an error from this step, please take note of the error and when asking for support be sure to include it, as odds are it will tell you everything you need to know in order to overcome the error.


The settings menu

The settings menu

Several aspects of Moksha can be customized. Most such customization, must be done from graphical user interfaces (GUIs), as opposed to from the command-line or via editing text files. Customization options, accessible via a GUI can be found under the “Settings” section of the menu that appears on click-clicking the desktop or the start gadget.

Application Menus

Click Menu Settings

Select Menu Settings

Go to Settings→All→Input→Menu→Menu Settings to change your application menus.

Select your Menus. See for example I have selected my LXDE application menu

Select your application menu

Desktop Backgrounds

Click Picture

Click Picture to set a picture on your computer as your desktop background.

To change your desktop background go to Settings→Wallpaper, press “Picture” and choose a picture on your computer to be your wallpaper. If you have problems changing your desktop background, I recommend changing the permissions of ~/.e/e/backgrounds with:

user $  chmod 777 -R ~/.e/e/backgrounds

and trying again.

Keyboard Shortcuts

Click Key Bindings

Select “Key Bindings”

Go to Settings→All→Input→Key Bindings and select your key bindings in the window below. To create a new program launcher click “Add”, press what keys you want in the shortcut, then go to Launch→Command and type in what command launches the program. Then press “Apply”. For example, for qBittorrent, I use the Alt+Q keyboard shortcut. The command I use to launch it is qbittorrent %U.

Choose your Key Bindings

Select your key bindings


Click 'Load' to load a module and 'Unload' to unload it.

Choose which modules you load or unload.

There are several modules you can load under Moksha, which all add functionalities to Moksha. To choose which are loaded and which are not go to Settings→Modules, in order to open the window shown above. There are also several modules maintained by Jeff Hoogland that are specifically designed for Moksha. They are found in Hoogland’s moksha-modules-extra GitHub repository. To download them and install them all with the minimum of bandwidth used, I recommend you use this script:


Use this window to add or remove shelves from Moksha

You can add new shelves with this dialogue and delete existing ones. In order to customize existing shelves go to “Contents” or “Settings”.

In order to customize your shelves (which can look like task bars or docks, depending on how they are set up) go to Settings→Shelves.


To set your theme go to Settings->Theme and select your theme from the menu that appears.

To set your theme go to Settings→Theme and select your theme from the menu that appears.

One of the most important customization, in my opinion, is to install the theme you want. To add a new theme, I recommend you add the following to your ~/.bashrc script:
then run:

user $  source ~/.bashrc


user $  theme <THEME>

where <THEME> is the Moksha theme you want. To find a theme you want I advise you go here. After you have installed the theme, you still have to set it as your current theme. The default Moksha theme of Bodhi Linux is Moksha Radiance, to get install it run:

user $  theme MokshaRadiance

. You can also change the GTK+ and icon themes used by programs running under Moksha by going to Settings→All→Look→Application Theme.

External links


An Introduction to Bash Scripting on Sabayon

31 October 2015 Command-line interfaces, HOWTOs, Overviews, Unix shells 1 comment

optipng 0.7.5 running under Bash 4.3.39 in LXTerminal 0.2.0

OptiPNG 0.7.5 running under Bash 4.3.39 in LXTerminal 0.2.0


  • Links to Wiki articles are provided in this post for those that wish to learn more, but it is important to note that I cannot guarantee their accuracy.

Bash, also known as the Bourne-again shell, is a Unix shell and command language, that is developed as part of the GNU Project. Along with the Linux kernel and package management system, I would rank Bash as one of the three most important components of a Sabayon Linux system. Without it or some other Unix shell in its place, one’s ability to interact one’s system would be very limited and difficult.

It was originally developed by Brian J. Fox in 1989 and has since become the most widely used Unix shell, with the vast majority of Linux distributions using it as their default command shell (only notable exception I have come across is Deepin, which uses Zsh) and since the release of 10.3 in October 2003 is has replaced tcsh as the default command shell for OS X.

In this post I will give some necessary background on Bash and its predecessor, the Bourne shell, as well as some basic scripting in Bash, some applications, etc. It is important to remember I am not an expert at Bash or Bash scripting, I have even had doubts I could even write an entire post on Bash scripting. It is important to note too that this post is nowhere near comprehensive on this topic, as the only type of text I, or anyone, could write that would be comprehensive on this topic would be an entire several-hundred page book, not a dozen-or-so-page blog post. This post just gives you some of the tools to do many of the basic things a novice or intermediate user of Sabayon would like to be able to do with Bash.


Brian J. Fox (1959-), the original developer of Bash

Brian J. Fox (1959-), the original developer of Bash

The development of Bash began in January 1988, when Richard Stallman, the founder of the GNU Project and the Free Software Foundation (FSF), became dissatisfied with the previous author of the GNU shell’s failure to meet the required deadlines and decided, instead, to get FSF staff member, Brian J. Fox to write a free imitation of the Bourne Shell.1 Later in June 1989, the first public release of Bash was made, 0.99 (which was a beta release) and until mid 1992 (when Bash 1.12 was released), Fox remained the lead developer of Bash.2 When Fox left the FSF in mid 1992, Chet Ramey took over responsibility for Bash’s development, which he has kept to this very day.3

Other Unix Shells

The Bourne Shell was one of the first official Unix shells to be developed and was first developed in 1977. I am using the phrasing “official Unix shells”, to draw attention to the fact that the Bourne Shell was developed at Bell Labs for use by Research Unix, which was the original Unix system. The Bourne Shell is named after Stephen Bourne, its original developer.

While Bash was originally developed as a free “imitation” of the Bourne Shell, it also has features that it borrows from other Unix shells: including the C shell and the Korn shell. The C shell (csh) is a Unix shell that was originally developed by Bill Joy — the author of the Vi text editor (which is a direct ancestor of Vim) and was first released in 1978 (and is still under active development today). Its chief distinguishing feature is that its syntax is similar to that of the C programming language. A notable descendent of C shell that is also widely used today, is tcsh (the TENEX C Shell), which before release 10.3 was the default shell of OS X. The Korn shell (ksh) was one of the Unix shells developed at Bell Labs for Research Unix, although unlike most other of the original Unix shells it is still under active development today.

Along with these shells, another free Unix shell that has gained notoriety, that I feel is worthwhile mentioning is the Z shell (Zsh). Zsh was first released by Paul Falstad in 1990 and at the time Falstad was a student at Princeton University. Since then Zsh’s development has become coordinated by Peter Stephenson. What is notable about Zsh, is how feature-packed it is. It has many of the same features as Bash, but it also has spelling-correction, easier customizability and a few other features that Bash lacks.

All free Unix shells that are available for Gentoo or Sabayon systems are located in the category of app-shells within the Entropy Store, Portage Tree and Gentoo Portage Overlays. To show them all from the command-line run:

user $  eix -C -c “app-shells”

Changing Unix Shells

On Unix/Unix-like platforms it is possible to change your login shell using the chsh command. For example, to change your login shell to Zsh (assuming it is installed), run:

user $  chsh -s /bin/zsh

and then reboot.


A natural question, that is asked by everyone, that is introduced to Unix shells, is “What is a Unix shell, exactly?” While this question sounds simple and straightforward, the answer is difficult to put into words, without it being either too generalized and vague, or too focused on specific examples. So I am going to air on the side of generalization and say that a Unix shell, is a command-line interpreter (CLI) that provides a familiar interface by which users can interact with the Unix4 system. Take the example of Bash, which is started whenever you open up a terminal emulator (TEE) or start tty1 (with Ctrl+Alt+F1) within most Linux systems, provided you have not set your default shell to something other than Bash. It interprets every command you type into the TEE or tty1 and can make changes to your system, accordingly. On most Linux systems, Unix shells are stored in the file directory /bin. You can list them all by issuing the command:

root #  cat /etc/shells

for me, for example, on my Sabayon machine this gives the output:

Bash and other Unix shells, have their own unique syntax or language (that is, how commands are passed onto Bash and other Unix shells), although most text editors (TEs) group all shell scripting languages together and call their collective syntax or language, “Shell script” or even just “sh”. Examples of such TEs include: Atom, gedit and SciTE. They can do this without a problem in most cases because Unix shells share quite a lot of their syntax with one another.

Another important concept, for one to understand in order for the rest of this post to make any sort of sense, is that of a script. Scripts are programs that can be interpreted from within a run-time environment (RTE) and they automate the execution of tasks that would otherwise have to be performed manually, one-by-one, by a human operator. In the case of shell scripts, including Bash scripts, the RTE in which the script is interpreted is the Unix shell.

Bash and Files

Bash scripts usually have the file extension of .sh, although some have no file extension. When Bash is started as an interactive, non-login shell (for example, from within a TEE) it first reads ~/.bashrc. When it is started as an interactive, login shell (like when it is started within tty1) it first reads /etc/profile, ~/.bash_profile, ~/.bash_login and ~/.profile. Commands executed in Bash are also recorded in ~/.bash_history. Commands interpreted by Bash are case-sensitive.

Basic Syntax

The Bash syntax has several distinct components, which can be classed as keywords and special characters, bulletins, variables, functions, tests and conditionals.

Keywords and Special Characters

Keywords and special characters (KSCs) are an important concept to understand, they are words, or symbols, that have a special, set meaning when scripting in Bash. Examples are listed in Table 1.

Table 1: Some Keywords and Special Characters Permitted in Bash
KSC Meaning, or usage Example(s)
Used to define functions. Curly braces can also be used to just group lines of code together.
Used for tests, double square brackets are only available in more advanced Unix shells such as Bash, ksh and Zsh.
tests whether the input variable, $1 exists.
# Whatever follows is interpreted by Bash, as a comment, for human operators to read but to be left uninterpreted by Bash.
! Returns the reciprocal (opposite) or negates of what follows it.
(which returns 0 (true) if the variable X does not equal 3, or 1 if it is equal to 3).
$ Evaluates what comes after it, such as a mathematical expression in double square brackets. echo $[3 * 2] returns 6.
| This is called a pipe and it sends the output of a command through another. For example, A | B does A and sends its output through B. The following example downloads the source code tarball of the 1.1.0 release of Atom and pipes it through tar and gzip to decompress it.5
; Allows several commands to be executed on the same line.
~ Denotes the home directory. For example, as my username is fusion809 on my Sabayon machine, my home directory is /home/fusion809.
takes one to current user’s home directory. If it is run as root it will take one to one’s /root.
- Can be used as the arithmetic operator, minus, or as the previous working directory.
takes one to one’s previous working directory.
* Wildcard operator, can take on any value. Can also be used for multiplication. If you have a directory, ~/VirtualBox on your machine and no others starting with the prefix ~/Virtual then:

should change your current working directory to ~/VirtualBox.
. Serves as an equivalent to the source bulletin and as an equivalent to pwd As source (the following will execute every file with the extension .sh in the ~/Shell directory):

whereas as pwd:

which causes no change in current directory.
.. Denotes the parent directory If I am working in the ~/Shell directory, and run:

my present working directory (pwd) would then be ~, my home directory.
&& Executes subsequent commands, provided the preceding command(s) were executed without error. For example, A && B does A and then B, provided that A is executed without error. While A && B && C would do A, then if A returns no error, it would perform B and if A and B ran without error it would then run C.
Conditional statement, checking whether inputs match. case starts them and esac ends them.
Used in for loops. for begins the loop, do enacts commands and done and finishes the loop.
Used in if conditionals.
in Used when dealing with lists This script should, if passed an argument open Atom to ~/Shell/$1.sh, otherwise ask the user to select from the list of shell scripts in ~/Shell of which one to open in Atom.
select Gets users to select from a list of options.

until, while and time are some other keywords that are not mentioned there, as I do not know enough about them to really comment on them. Keywords can be used as variables but I would not advise this, as this can quite easily become confusing.


Bash variables are defined using equal signs. They can be made global (making them available for all processes) or local (making them available just for the script at hand). Local variables are defined by just using an equal sign, for example:


while to define this variable globally, one would run:

export PYTHONPATH=/usr/bin/python


Several Bash commands (or bulletins) exist and some (but by no stretch of the imagination all — I do not even understand them all!) basic ones are explained in Table 2. It is worthwhile noting that all these commands are purely Bash commands, by this I mean, they do not call any command-line programs to do their work for them. See many commands you will see in Bash scripts are not Bash commands, per se, rather they are commands that use another command-line program such as mv or pwd to do the work, but they can be run from within Bash. Many of these programs are also borrowed from the GNU Project, namely its core utilities package (sys-apps/coreutils) and are stored in either /usr/bin/ or /bin/, directories.

Table 2: Some Basic Bulletins
Command Meaning Examples Manpage (HTML)
alias Set a synonym for a command or function alias.1p.html
cd Change directory.
changes one’s directory to /home/username/Documents.
date Outputs the date. Inputs/variables can be used to set the timezone and the format of the date given. This gives my local date and time in my preferred format:
export Set variables provided to it as environment, or global, variables. export.1p.html
history Outputs Bash history.
should show the last ten commands executed with Bash.
source Execute script(s) provided to it.
runs the ~/.bashrc script.


Tests are essential for conditionals. As their name suggests, they test to see whether or not a condition is satisfied. If the condition is satisfied they return 0, while if the condition is unsatisfied they return 1. Square brackets (which are a bulletin, by-the-way), [...], are used for tests, although double square brackets ([[...]]) can also be used for this purpose since Bash 2.02. The difference, from what I can tell, between single and double square brackets is that double square brackets allow one to perform more advanced tests than single square brackets. Single square brackets are also POSIX compliant and are found on all Unix shells.6


In Bash scripts conditionals use the output of a test and perform an action accordingly. Conditionals usually involve at least one of the following keywords: case, if, else, elseif and fi.


Functions are essentially convenient ways we can group pieces of code together, so as to give them order and make them more logical. Quite often functions are designed to take input and use it to generate an output, or to perform a task, although some functions require no input. All Bash functions share two main things in common: the use of the word “function” and the fact the function’s contents are contained within curly braces {...}.


Loops (which involve the for keyword), in Bash scripts, are used to automate the performing of tedious tasks that are sufficiently similar to one another.


Selectors (marked by the select keyword) gives users choices as to which input(s) the rest of the selector block uses.


The primary value of Bash scripts is to automate tasks that would otherwise have to be done, over a longer time-frame by a human operator. I personally use shell scripts to make my life, when I am at the command-line, easier.

In my ~/.bashrc file I have links to several shell scripts stored in my ~/Shell directory. Both my ~/.bashrc and the shell scripts in my ~/Shell directory can be found at this GitHub repository. Here is my current ~/.bashrc file:7

I have at least three dozen functions I have defined in shell scripts located in the ~/Shell directory, but here I will mention some of the more interesting, or useful ones for Sabayon users, in general.

Interesting Scripts8

You may have noticed that I am hosting HTML versions of several Linux man pages within the /man subdomain of this blog. I generate them using a function contained within ~/Shell/man.sh called manhtml. For example, to generate emerge.1.html I ran user $  manhtml 1 emerge. Here are the contents of ~/Shell/man.sh (showing all the contents as manhtml depends on other functions to work):

while here is a function I created to help me install Moksha themes (it appears differently in my ~/Shell/other.sh file, as this form is mostly to walk you through how it works):

to install a new Moksha theme you would run user $  theme <THEME> where <THEME> is, of course, the theme’s name (how they appear in their respective GitHub repo’s URL).

Useful Functions for Sabayon Users

The following are some functions that, depending on how you operate on Sabayon, may be helpful.


The following are taken from ~/Shell/equo.sh and they are functions (with aliases for said functions) that essentially automate some common actions one may perform with Entropy. They are not all the lines of code in equo.sh, they merely represent some of the more commonly-used codes. It is important to note some of these functions need not be defined as functions, they could instead be defined as aliases (using alias NAME=CODE where NAME is the function’s name and CODE is what is between the curly brackets).


Here are some lines from my emerge.sh script.

Free Help Resources

Further Reading

NOTE: All the following links are to free PDFs


  1. Source: email from 1987
  2. Source: Chet Ramey’s Scribd document
  3. Source: Bash Webpage
  4. Or Unix-like, in the case of Linux distributions such as Sabayon
  5. Note, I previously did not know how to pipe the output of wget through tar until I asked this question at Unix & Linux StackExchange. The defining of an ATOM variable (instead of just combining it into the second line) is mostly just for space restrictions within this table
  6. Source: Server Fault
  7. The for loop I got from the answers to this question at Unix & Linux SE
  8. Which is in the eye of the beholder of course, you may not find these interesting at all
  9. Its general topic is programming, so it is suitable for shell script-related questions. I have asked two questions there relating to shell script, as of 31 October 2015, both were resolved within an hour.
  10. As of 31 October 2015 I have asked 8 questions relating to shell scripts there and seven have been answered. Each of those that have been answered were resolved (that is, given an answer that solved whatever problem I had) within a day of me asking them.

Package Management on Sabayon

12 October 2015 HOWTOs, Installation guides, Overviews, System software 2 comments


  • This post contains links to wikis, including the Gentoo and Sabayon Wikis and the English Wikipedia. The information contained on these pages is subject to frequent changes and no one, myself included, can guarantee their accuracy at any given time.
  • Any instruction involving Portage, has the capability to break your system and cause other problems, so if you follow them you and you alone assume any and all responsibility for the consequences!

Often, on this blog, I write posts regarding installing software with Sabayon’s two package managers: Portage which it borrows from Gentoo and Entropy which is wholly original. I felt I would dedicate this post to both package managers, giving you some tips on how to use them safely and most efficiently. Generally speaking when it comes to Sabayon, unless you know what you are doing (for future reference users that “know what they are doing” in this context will be referred to as competent Sabayon users), you are recommended to only use Entropy as your package management system (PMS), as working with Portage is more risky and mixing Entropy with Portage is known to quite easily lead to system breaks. I mix the two, even though I would not call myself a competent Sabayon user, because quite often Entropy does not provide the software I want, while Portage can.

This post will cover some of the basics of using Entropy and Portage and how to use them together, in the safest way possible. It will also cover other related topics like using Layman to add overlays. You will probably notice that the command-line is featured heavily in this article, with little mention (usually all they will get is about a sentence mention each, if they are really notable) of graphical user interface (GUI) front-ends for these programs, this is because I tend to find command-line front-ends for package managers are more stable than their graphical counterparts.

Preliminary Information

Entropy, Layman and Portage are all written in Python. Entropy is maintained by Fabio Erculiani and other developers of Sabayon, while Layman and Portage are both maintained by the Gentoo community. This section will cover some of the preliminary information for each of these programs, including their command-line syntax, so as to make the rest of this post easier to understand.


Screenshot of Porthole running under KDE Plasma 5

Screenshot of Porthole running under KDE Plasma 5

Portage is a package management system that is arguably the most powerful Linux PMS available today. It is written in Python and Bash script, so as to afford users the ability to script with Portage. Portage installs, removes and upgrades software using the instructions contained in ebuild (that is, Bash scripts with the file extension .ebuild) files, which are stored within the “Portage Tree” which is /usr/portage, by default. This tree, only contains ebuilds from the Official Gentoo Overlay (OGO, you can search this overlay online here), ebuilds in overlays added with Layman are added to another location, /var/lib/layman. Normally Portage installs (or “merges“) software from source code, so as to maximize the control users have over the features their software has, but some pre-compiled binary packages exist in the OGO for software that would otherwise take several hours to compile. These packages are in .tbz2 file format and are created by running emerge with the --buildpkg or --buildpkgonly options enabled. Installing software from source code may also improve the performance (minimizing resource usage) of software installed this way.

Portage affords users this extra control via USE flags, which are “keywords that embodies support and dependency-information for a certain concept” (quoted from the Gentoo Handbook), in other words they are keywords that allow users to decide which (if any) optional package features (like language bindings, for example) will be built, when the package itself is built. These USE flags can be enabled or disabled for individual packages (via modifying files in the directory /etc/portage/package.use) or for all packages (via editing the USE="... line in /etc/portage/make.conf. USE flags should not be confused with package keywords (individual package keywords can be found in the directory /etc/portage/package.keywords, editing keywords for all packages can be done by editing the ACCEPT_KEYWORDS="..." line in /etc/portage/make.conf), which are entirely separate keywords, that detail architecture support (x86_64 vs. x86) and a few other features. Likewise packages you do not want Portage to emerge under any circumstances (which can be called masked packages) can be added to files within the directory /etc/portage/package.mask.

Portage is traditionally a command-line package management system (invoked by the command emerge), with no official graphical front-ends available, but a few unofficial graphical front-ends exist in the OGO, of which the most popular is probably the GTK+ based Porthole (app-portage/porthole).

The OGO contains over 18,500 software packages, as of October 2015, and while this may seem like quite a fair number (which it is) there will always be some people that will want to install software that is not in the OGO. To do this it is advisable to search the GPO website, for the package you would like and then add the overlay that contains the package you want with Layman.

Emerge Syntax

According to Portage’s Manpage1, emerge commands have the following format:

root #  emerge [options] [action] [ebuild | tbz2file | file | @set | atom]                                       (1)

This can be confusing to users not familiar with the formatting used by Gentoo’s Manpages (or Linux Manpages in general, for that matter), but I will attempt to explain. Before I do, I need you to get into the mind-frame you had when you first learnt algebra in high school, where variables (like x or y) could be substituted with numbers, letters, other characters or a combination of any, or even all of these. With this mind-frame the above generalized format of emerge commands will make more sense, as all words in that command except for root and emerge can be substituted, depending on what you want to do with Portage.

What is in square-brackets ([...]) are optional parts of the command (that is, they can be omitted) and when you are writing an actual command you omit the square brackets and substitute the word inside with any of a set of possible values it can take on. Some (not all, I do not even understand them all!) possible values options and action can take on are covered in the tables below. Multiple options can be combined with certain actions, often using the shortened notation. For example, to combine the ask and verbose options when emerging GNU Octave, one can run the shortened form root # emerge -av sci-mathematics/octave or the full-lengthed form root # emerge --ask --verbose sci-mathematics/octave. The vertical lines or pipes, as they can also be called, which is |, in (1) means the options separated by it and between the square brackets are mutually-exclusive options (that is, you either pick one or you pick none, depending on what you want to do). To save time, I will call the following part of (1) “input“:

[ebuild | tbz2file | file | @set | atom]

Sets (@set in the “input”) are essentially a useful way of specifying a large group of packages. There are six sets found in a default install of Sabayon, more can be created by users with root access by them editing files in the directory, /etc/portage/sets. Running root #  emerge --list-sets should list all available sets. ebuilds are just the names of packages you want to install. At a bare minimum they should be the package’s name (case-sensitive), without its category (e.g., wordpress for www-apps/wordpress), but sometimes specifying a package’s name without its category leaves some ambiguity (that is, there may be more than one package in the Portage Tree or unofficial overlays added with Layman, that has the name specified), so it is often safer to specify the category also. Some people may want to specify the specific package version they want too, to do this add an equal sign before the category and specify the package version after the package’s name, for example running emerge =sys-apps/portage-2.2.20 should install Portage version 2.2.20. Files are files that have been created by installed packages. tbz2file, as one can probably guess are any binary packages created by emerge itself, in the .tbz2 file format that one wishes to install. Atoms (atom) are essentially the same as ebuilds, only with bounds on their version numbers specified. For example, emerge <dev-lang/python-2.0 should install the latest version of Python available before version 2.0.

Table 1: Options for Emerge
Long Short Meaning
-a Ask before running the action.
–autounmask [y|n]
N/A This option is enabled by default and it basically allows emerge to unmask packages as required and write changes for package.use. Possible forms this option can take on are --autounmask=y, --autounmask=n (which will disable this option and unmasking/package.use changes will not occur) or --autounmask.
–autounmask-write [y|n]
N/A This option is similar to --autounmask, except it can write to package.use and other configuration files directly.
–buildpkg [y|n]
-b By default this option is disabled, but when enabled it causes emerge to install the package(s) and it also creates binary package(s) from the installed package(s) (file format: .tbz2) in PKGDIR (which is specified by /etc/portage/make.conf, by default it is /usr/portage/packages).
-B This option, which is not enabled by default, will only create binary package(s) and not install the package(s) specified to it.
-U Tells emerge to include installed packages where USE flags have changed since installation.
-d Show more detailed debugging information.
-D With this option emerge will look at the entire (or “deep”) dependency tree (not just the immediate dependencies of the package it is emerging, which it does by default) for updates.
-e Reinstalls package and all deep dependencies.
–keep-going [ y | n ]
N/A Continue as much as possible after an error.
-N Reinstall packages that have had their USE flags changed since installation. This option is more comprehensive in the packages it reinstalls than --changed-use.
-O Installs specified packages, without installing any dependencies. This option may cause package breakage.
-n Skips packages that are already installed.
-1 It will emerge the package as normal, but will not add the packages to the world file for later updating.
-o Install the specified package(s) dependencies, only. This is the emerge equivalent to APT’s apt-get build-dep.
-p This option causes emerge to display which packages would have been emerged, had the pretend option not been used.
–quiet [y|n]
-q This option, although results do vary, should minimize the output provided by emerge.
-u Updates packages to the best version available (not necessarily the latest, however).
-v This option causes more details to be given from ask and pretend commands. These details include GNU info errors and (for the pretend command) it will print USE flags.
–with-bdeps [y|n]
N/A During dependency calculations, build time dependencies that are not strictly required will be included. For installation actions this defaults to n, while for depclean actions this defaults to y.
Table 2: Action values for Emerge
Long Short IR? Meaning
None N/A Yes If no action is specified then emerge will merge all packages specified and their dependencies.
N/A Yes Run specific configuring processes that must be done after the package is emerged. The best example for this I can provide are the MariaDB and MySQL packages. Configuring these packages is required in order to set up a database with them.
-c Yes Removes packages not associated with any merged package.
-h No Displays some basic syntactic information, although if you really want some documentation for emerge from the command-line use man emerge.
-P Yes Remove all but the highest installed version of the package specified.
N/A No Causes portage to check and update the dependency cache of all ebuilds in the portage tree.
-r No Resumes the last merge, if said merge was cancelled due to errors.
-s Yes Search for packages who’s name matches with the supplied case-insensitive string.
-S Yes Search the Portage tree for string in package names and descriptions.
N/A No Updates all the ebuilds in the Portage Tree. You should do this once a week, at least. The first time you do it, this will take quite some time (potentially up to a few hours). To save time the first time you do this you may wish to run emerge-webrsync which will download the Portage Tree as a tarball.
-C Yes Unmerges (that is, uninstalls) software packages specified.
WARNING: This command ignores packages that may depend on the unmerged packages. For a more dependency-conscious and hence safer version of this command use the --depclean or --prune options.
-V No Display the version number of emerge.




Wiki Articles


Layman is a command-line tool for managing Portage overlays. It can be installed with Portage (from the OGO) using the command:

root #  emerge -av app-portage/layman

or with Entropy using the command:

root #  equo i -a app-portage/layman

I would recommend installing Layman using Entropy as it is less error-prone and the Layman package it installs was compiled with all the USE flags required to add every type of overlay available (including Bazaar (bzr), Git, Mercurial (hg) and Subversion (svn)). Layman-added overlays (and the ebuilds contained within them) are stored in /var/lib/layman/.

Layman Syntax

The basic syntax for Layman is:

root #  layman [options] [action]

As with emerge, I am not going to cover every option and action available for layman, as that would take too long, plus this is not meant to be a substitute for the manpages of the package managers and other tools covered in this post. Some of the more important/frequently-used actions and options are covered in tables 3 and 4. Please note that all actions when given in long form, if they require input (like --add does) this input must be specified with an equal sign and no spaces. For example to add the “sabayon” overlay you may run:

root #  layman –add=sabayon

or in shortened notation:

root #  layman -a sabayon

It is important to note that while this technique will add the sabayon overlay to one’s machine not all overlays can be added this way, as some overlays are not within Layman’s default list of available overlays (which I will henceforth refer to as the reference list). To view the reference list, run:

root #  layman -L

while to see the list of overlays currently installed, locally, on your machine run:

root #  layman -l

To add a new overlay that is not within the reference list, run:

root #  layman -o <URL of repository XML file> -f -a <overlay name>
Table 3: Options for Layman
Long Short Meaning
-N Remove colour codes from Layman output.
-q Reduce output.
-Q Takes a numerical value between 0 and 4 to determine the amount of output provided. 0 means no output, 4 means full output.
-v Makes Layman give more output details, such as a description of the overlays you download.
Table 4: Actions for Layman
Long Short Meaning
-a Add overlay.
-d Delete overlay. Specify “ALL” to delete all locally installed overlays.
-D Disable overlay. Specify “ALL” to disable all locally-installed overlays.
-i Display all available information about the overlay.
-L List all available overlays. Note that these overlays are not necessarily installed on your system.
-l List all locally-installed overlays.
-r Re-add overlay(s) specified, to re-add all overlays, use the input “ALL”.
-s Synchronize (or in other words, update) overlay(s) specified. To sync them all use the input “ALL” or use the
-S option mentioned below.
-S Update all overlays.



Rigo Application Browser running under KDE Plasma 5

Rigo Application Browser running under KDE Plasma 5

Entropy, is a PMS that was specifically designed for Sabayon by Fabio Erculiani, the original creator of Sabayon. Its first unstable release to be added to Sabayon was in July 2008 when Sabayon 3.5 was released and its first stable release to be added to Sabayon was made in May 2011 with the release of Sabayon 6. Unlike Portage which is primarily designed to install source code packages (although it can also install binary packages), Entropy is designed to work with binary packages only. Binary packages take less time than source code packages to install and requires less user know-how and input. Entropy is also unique in that it has two official front-ends: command-line/textual (Equo) and graphical (Rigo). I personally favour using the command-line for installing packages on Linux distributions, because in my experience graphical installers are more prone to crashes during installation than their command-line/textual counterparts.

Compared to Portage, Entropy is far more simple to use, if you go to the Entropy Store you can see the USE flags used to compile the software packages provided by Entropy, as all packages provided by Entropy had to be compiled with Portage on another machine first (in .tbz2 format). Entropy contains packages from the Portage Tree and packages from Sabayon’s own overlays, which are called sabayon and sabayon-distro, respectively. Entropy is also safer to use and support for using Entropy to install packages is far better than support for Portage-installed packages on the Sabayon forums.

Equo Syntax

The generalized syntax for Entropy’s command-line front-end, Equo, is:

root #  equo [action] [options] [ebuild | atom]

Some (but by no stretch of the imagine all) options and actions for Equo are listed in tables 4 and 5, below. Note some options are only available for certain actions, for details see the man pages for Equo and its various actions (e.g., run man equo install for the equo install manual). One action and another option that are not covered in these tables, that I felt were worthwhile mentioning, are repo and mirrorsort, respectively. The command:

root #  equo repo mirrorsort <REPO>

where <REPO> is the name of an Entropy repository (e.g., sabayonlinux.org, sabayon-weekly or sabayon-limbo), can be used to optimize the order of preference for the repository’s mirrors, hence, potentially, accelerating the process by which Sabayon downloads software packages.

Table 5: Options for Equo
Option Meaning
-a, --ask Ask before performing actions. For example equo i -a [ebuild] will ask you before it will install the package specified by the ebuild argument.
--deep Reinstall dependencies, even if unnecessary.
-h, --help, help Print help information.
-o If given to the “install” action this option will cause only the package’s dependencies to be installed. This is the equivalent to running apt-get build-dep for APT.
-p, --pretend Show what would be done, had this option not been given.
--purge (for upgrade) it will remove unmaintained packages, if any.
-q, --quiet Quiet (reduce) output.
-v, --verbose Verbose output.
Table 6: Actions for Equo
Long Short Meaning Manpage
cleanup N/A Remove downloaded packages and clean temporary directories. equo-cleanup.1
config N/A Configure installed packages. equo-config.1
deptest dt Look for unsatisfied dependencies. equo-deptest.1
install i Install software. equo-install.1
libtest lt Look for missing libraries required by other packages. equo-libtest.1
mask N/A Mask packages given as input. equo-mask.1
remove rm Remove packages given as input. equo-remove.1
rescue N/A Tools to rescue system equo-rescue.1
search s Search for packages in repositories. equo-search.1
unmask N/A Unmask packages given as input. equo-unmask.1
update up Update repositories. equo-update.1
upgrade u Upgrade packages that have been updated (in the software repositories) since they were installed, or since you last ran this command. equo-upgrade.1


Mixing Entropy with Portage

By default Entropy and Portage act fairly independently of one another. In order for you to use them together, you must tell Entropy that you are also using Portage to install packages by running:

root #  equo rescue spmsync

whenever you emerge, unmerge or update a package. I have this saved in my ~/.bashrc (for root user) as the function spm, so as to make it easier for me to run it when necessary. What this will do is it will cause packages you installed with Portage to be acknowledged by Entropy, as otherwise Entropy has no clue as to their existence. After this you may also wish to mask packages you installed with Portage, so as to prevent Entropy from attempting to upgrade or remove software installed with Portage. To do this run:

root #  equo mask <PACKAGE>

To prevent Entropy from downgrading emerged packages you need to edit


and uncomment (removing the hashtag #) the line

ignore-spm-downgrades = enable

Packages installed with Entropy are almost always safer (less likely to lead to system breaks or have bugs) than their Portage-installed counterparts, so when you install a package with Portage that has several non-installed dependencies I would suggest you install as many of these dependencies as possible with Entropy before you merge the remaining dependencies and the package itself with Portage.

Further Reading

The Algorithm

Occasionally, while browsing the internet, I find a program I would like to install on my Sabayon machine. Here is the algorithm I follow to install it:

    1. I search for whether or not said software is available in the Entropy Store. If it is there I install it with Equo (e.g., via running root #  equo i <PACKAGE>), if not I proceed to the next step.
    2. I search for whether or not said software is available in the main Gentoo Overlay. If it is there I install it with Emerge (e.g., via running root #  emerge -av <PACKAGE>), otherwise I move onto the next step.
    3. I search for whether or not the software is available in any unofficial overlays. If it is, and the version number is acceptable (usually I prefer the latest stable version of a software, but sometimes I will settle for fairly recent stable versions) I may add the containing overlay with
      root #  layman -a <OVERLAY>

      then sync both Portage and Layman with (I also have this added as a function called sync in my ~/.bashrc script)

      root #  emerge –sync && layman -S

      and then emerge the package with

      root #  emerge -av <PACKAGE>

otherwise I proceed to the next step. If the package has several dependencies I try to install as many as possible with Entropy, before I emerge the remaining dependencies and <PACKAGE> itself. Often using pretend instead of ask options (emerge -pv... instead of emerge -av...) will be helpful if you want a list of packages to install with Entropy. Sometimes emerge will say you need to adjust your USE flags (stored in /etc/portage/package.use/), package keywords (stored in /etc/portage/package.keywords), list of accepted software licenses (stored in /etc/portage/make.conf) and alike to install the package you want.

  1. If all else fails I get the source code and try compiling and installing it myself. This step is last, because this step is very error prone if, like me, you do not know an awful lot about compiling software or programming, in general. This step depends on the instructions in any INSTALL or README file included with the source code. If these files do not exist I use my knowledge on common compiling methods to install the software. For example, if the source code is written in C/C++ often there will be an autogen.sh or configure file somewhere in the source code base directory, which I will run (usually by opening up a terminal emulator and running user $  ./<FILE> where FILE is either autogen.sh or configure)) and read the output of. If the output includes an error, concerning some missing dependency, I will try to install said dependency (following the same algorithm outlined here) and re-run the autogen.sh/configure script or if the dependency is on my PC already I will try giving the autogen.sh or configure file a PATH variable pointing to the dependency’s location on my system when I re-execute them. If no errors are encountered when running these scripts, or I manage to fix them with the methods I just mentioned I then run
    user $  make


    user $  sudo make install

    While if the source code is written in Python I look for a setup.py file and run

    root #  python setup.py install
  2. If errors are encountered at any of these steps (by errors I do not include the absence of available software packages as errors) I also attempt to seek support. For example, if the failure happened with an added unofficial overlay I often find the GitHub repository that houses the overlay and create a new issue for said repository. This process of getting support often occurs quite slowly, taking several days, at least, to get any solution to the problem, so often if failures happen I move onto the next step of this algorithm (if there are any steps left) before I report the failures.




An example of OpenRA running

OpenRA (games-strategy/openra) is a free and open-source futuristic strategy game. For me, it reminds me of one of my favourite Windows games, Outlive. OpenRA is unusual in that it is not available in the Entropy Store, although a few ebuilds for it do exist in the Portage Tree, although it is worthwhile mentioning that these ebuilds are often out of date. For example, as of 12 October 2015 the latest ebuild available in the Portage Tree is for version 20141029 (note how this number represents the date of the release, 29 October 2014), while the latest release is 20150919 (released 19 September 2015). There are unofficial overlays (such as games-overlay) that contain more recent versions of OpenRA, although as of 12 October 2015 they still do not contain the latest release of OpenRA.

To install the latest version available of OpenRA on Sabayon one has four main options:

  1. Emerge the package from the Portage Tree. This will get you release 20141029, at best. I have not tried this due to how old a version this package is. To do this simply run
    root #  emerge games-strategy/openra
  2. Add the games-overlay with Layman and emerge the latest version available from it, 20150614. This option I have not bothered with due to the fact it contains an old version of OpenRA and is an unofficial overlay (which makes it higher risk for system breaks and other issues). To do this run
    root #  layman -a games-overlay
    root #  emerge –sync && layman -S
    root #  emerge games-strategy/openra::games-overlay
  3. Add the dr overlay (not available with Layman) and emerge the latest version, 20150919. This option I have not done, due to the fact it needs freetype unmerged and that would break my system. To do this run:
    root #  layman -o http://github.com/cerebrum/dr/raw/master/repo.xml -f -a dr
    root #  emerge –sync && layman -S
    root #  emerge games-strategy/openra::dr
  4. Compile the source code yourself and install OpenRA from that (which will get you the latest version of OpenRA, 20150919). This option I have succeeded in doing and is how OpenRA is currently installed on my system. To do this I ran:
    user $  wget -c https://github.com/OpenRA/OpenRA/archive/release-20150919.tar.gz
    user $  tar -xzf release-20150919.tar.gz
    user $  cd OpenRA-release-20150919
    user $  make dependencies && make all

    This does not add an executable of OpenRA to /usr/games/bin/ and hence running openra from the command-line will not start the game. So after this I also created a shell script file called /usr/games/bin/openra with nano (that is, I ran

    root #  nano /usr/games/bin/openra

    ) with the line mono --debug /path/to/OpenRA.Game.exe where /path/to is replaced with the path to where you built OpenRA from source code (which for me is /home/fusion809/Programs/OpenRA-release-20150919).

External links


SuperTux 0.3.3

SuperTux 0.3.3

SuperTux (games-arcade/supertux) is a free and open-source (licensed under GNU GPLv3) 2D platform game that was first released in April 2003. Its gameplay is very similar to that of the proprietary game, Super Mario Bros. The initial 2003 release was called “Milestone 1” (or if you would prefer a version number 0.1.3) and is the version of SuperTux available in the Entropy Store and the Official Gentoo Overlay (OGO). I have installed this version with Entropy, using:

root #  equo i games-arcade/supertux

This game is enjoyable, giving several hours of entertainment for me at least. Despite this, due to my preoccupation with using the latest software available, I looked to install the latest version of SuperTux (which are developmental, but still fairly stable, versions of Milestone 2 (or SuperTux 2) which is due to be released in December 2015). I tried installing it using the unofficial yarik-overlay and while this succeeded I found the most stable version provided by it (0.3.4) plagued by bugs. To do this I ran:

root #  layman -a yarik-overlay
root #  emerge –sync && layman -S
root #  emerge -av supertux

So after this, I decided to give manually building and installing it myself, a go. Then I got the latest tarball source code release (tar -xvf supertux-0.3.5a.tar.bz2 should do this from the command-line), decompressed it, changed into the supertux-0.3.5a directory and ran:

user $  mkdir build
user $  cd build
user $  cmake ..
user $  make
user $  sudo make install

this ran without error and the resulting SuperTux 2 installation (which by-the-way I have managed to keep on my system despite never removing my SuperTux 1 Entropy installation) was less buggy, in fact, I do not believe any bugs are left.

External links


  1. Specifically the emerge(1) manpage