Gentoo Wiki


This article is part of the HOWTO series.
Installation Kernel & Hardware Networks Portage Software System X Server Gaming Non-x86 Emulators Misc



This HOWTO will guide you through the install and setup of the Enlightenment Graphical Login Manager, Entrance.

Warning: CVS versions are bleeding-edge, and WILL, sooner or later, NOT compile, run, or work as you expect. Make sure you always layman --sync enlightenment before emerging CVS versions of software. When you emerge this software you will be presented with these words: "This is a LIVE CVS ebuild. That means there are NO promises it will work. If it fails to build, FIX THE CODE YOURSELF before reporting any issues." Live by them.



Entrance and its dependencies ebuilds are part of Vapier's Dev Overlay so the first thing you need to do is emerge and setup your layman overlay.

Follow the latter link above and add the enlightenment overlay though layman,

$ layman -a enlightenment
Warning: The default layman storage directory is /usr/portage/local/layman, you can change this setting and others in /etc/layman/layman.cfg. If you do, remember your specific paths throughout this article.

Once the overlay is added you need to use the appropriate package.keywords. There are two package.keywords supplied with the enlightenment overlay, one keywords the "live" CVS ebuilds the other keywords CVS snapshot ebuilds.

The easiest way to utilize these is to have a /etc/portage/package.keywords directory instead of the one regular file. Then symlink the appropriate package.keywords to /etc/portage/package.keywords/,

$ ln -s /usr/portage/local/layman/enlightenment/scripts/package.keywords.livecvs /etc/portage/package.keywords/

You can, if you must, cat the entries from the package.keywords to your /etc/portage/package.keywords file,

$ cat /usr/portage/local/layman/enlightenment/scripts/package.keywords.livecvs >> /etc/portage/package.keywords

but this will force you manually maintain it when changes are made to the overlay and it is not recommended.

Note: It's strongly advised that you sync your layman overlay before you update,
$ layman --sync=enlightenment


Before you start your emerge of Entrance you should check that everything is in order with the --pretend and --verbose options.

# emerge -pv entrance
Note: Make sure the "X" USE-flag is enabled in all enlightenment ebuilds.

Check that the ebuilds have the USE-flags you prefer enabled. If you feel that they do not, refer to the USE-flags FAQ for instructions on USE-flag handling. At this step it's also a good idea to double check that the ebuilds are ending with -9999 if you are using the LiveCVS package.keywords entries or -0.9.9.* if you are using the snapshot package.keywords entries, and said ebuilds should be emerged from overlay "/usr/portage/local/layman/enlightenment", if they are not, review the Preparing chapter again and look for typos and errors in your /etc/portage/package.keywords.

When you are satisfied with the results of emerge -pv, it's time for the actual emerge. To be on the safe side, you should emerge with the --ask option.

# emerge -av entrance

If emerge didn't halt due to broken code from the CVS repository, you should have successfully emerged Entrance. If emerge fails, the most advised thing to do is to wait about one day for code to get fixed, and try again the same emerge command.


To see all existing config options, run:

$ entrance_edit

And you can of course run:

$ entrance_edit -h

for instructions on how to use entrance_edit.

To change a setting, use this template,

$ entrance_edit --OPTION=VALUE

If the VALUE is a string, use quotationmarks.

Authentication Method

Note: You can skip this step if you compiled entrance with the 'pam' USE-flag and intend to use it. Entrance defaults to using PAM when available.

To have Entrance use Shadow as it authentication method, you need to change the auth setting.

Run as root:

$ entrance_edit --auth=2

To have Entrance use PAM as it authentication method, change the auth value back to 1.

Run as root:

$ entrance_edit --auth=1

Entrance at Boot


Gentoo uses a script called xdm to start the Graphical Login Manager, this script is supplied by xinit, this package is of course a dependency of X11 so you no doubt have this.

First check that xdm is set to start at the default runlevel with:

$ rc-status | grep xdm

If this command gives you nothing, you need to add it:

$ rc-update add xdm default

After this is done, you need to tell the startup script that it is Entrance you want to use. Open /etc/rc.conf and look for the DISPLAYMANAGER line.

File: /etc/rc.conf

Remove the comment(#), change "xdm" to "entrance" and you should be all set.

Note: Recent versions of Portage moved this setting to /etc/conf.d/xdm.


Init-NG users only need to add entranced to de default runlevel.

$ ng-update add entranced default

There is no need to change any settings in /etc/rc.conf


I had some problems with this installation. First, the Evas library; for who knows why, Entrance want the filename, so I just created a symlink from /usr/lib/ to /usr/lib/, and it worked like a charm.

Second, entrance wanted to execute a script named /etc/X11/Xsession, which doesn't exist; so I just created another symlink from /etc/X11/Sessions/Xsession.

Third, and more my fault, I used --theme=/usr/... ; you should just use --theme=FILENAME.edj.

See the discussion page for more.

Concerns or Compliments? Please use the Discussion section.

Retrieved from ""

Last modified: Wed, 27 Aug 2008 04:56:00 +0000 Hits: 50,657