Regarding the bug pythonhead discovered: Unfortunately I can't reproduce it. Did anyone experience the same problem?

Just to be clear, in case anyone else can verify it, this works fine,
when I have the same version in PORTDIR and PORTDIR_OVERLAY:
/usr/portage/app-foo/pkg/pkg-1.0.ebuild
/usr/local/portage/app-foo/pkg/pkg-1.0.ebuild

However if I only have:

/usr/local/portage/app-foo/pkg/pkg-2.0.ebuild

with no 2.0 version in PORTDIR, eix doesn't find PORTDIR_OVERLAY version 2.0.

- added: multi-line entries in ebuild and/or /etc/make.conf are parsed
variables declared without double quotation marks are recognized correctly as well as tab characters in PORTDIR_OVERLAY

- versions which are not tested on your architecture are now shown by default (previously: only with -v). I changed the prefix for such versions from [M~] to [-]

- cleaned the command line parser and implemented the quasi-standard getops() function which is used by almost any linux program
eix -s ist now default, so you can simply type "eix REGEXP" to search for packages.
(author: appro)

The new syntax:
eix now understands parameters like most unix programs, i.e. you update the database with eix -u. no parameter, for example

Code:

eix gcc

assumes -s and searches for a package. You can use multiple options after one - now, e.g. eix -nvS gcc.