Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 107201 - x11-wm/e won-t compile, wrong deps in the e-9999 ebuild
Summary: x11-wm/e won-t compile, wrong deps in the e-9999 ebuild
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: SpanKY
Depends on:
Reported: 2005-09-25 11:15 UTC by Marc V
Modified: 2005-09-25 14:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Marc V 2005-09-25 11:15:54 UTC
when you "unmask" the e-9999 ebuild, it wants to install some libs as deps which
is correct. The problem is that the cvs version of e17 MUST require the CVS
versions of the needed libs, because now you can run it with the old libs and it
won`t compile.

i.e., it requires EVAS, but it must require EVAS-9999

Reproducible: Always
Steps to Reproduce:
1. emerge e

Actual Results:  
it wont compile

Expected Results:  
it should install the CVS versions of the deps (masked libs which you have to
add to /etc/portage/package.keywords as -*), then it works as it should.
Comment 1 Marc V 2005-09-25 13:45:21 UTC


There are ebuilds in Portage for all EFL and most programs that use them. In 
addition to snapshots that are updated every few weeks, there are also live CVS 
ebuilds available. This can sometimes change though, sometimes there are only 
CVS ebuilds available for certain libraries/programs. Check the Gentoo package 
database to see the current situation. All CVS ebuilds have sudo as a 
dependency, so it will also be installed if you use the CVS ebuilds. It can be 
considered to be a security risk. The default sudo config file should not allow 
much though, so unless you edit it to allow insecure stuff it shouldn't be a 
problem on normal non mission-critical desktop systems. This is of course a 
question of opinion so you'll have to decide for yourself if you consider it a 
risk. Another thing you should know is that the CVS ebuilds obviously don't 
check md5sums. The CVS ebuilds will also use root for all steps of the 
installation and may not always work, depending on the current CVS situation. 
The snapshot ebuilds are only updated if nothing is seriously broken. 

The CVS ebuilds are marked with the -* keyword while the snapshots are marked 
~arch. Obviously neither the snapshots or the CVS ebuilds are marked stable. 
These ebuilds are maintained by Mike Frysinger ( If your 
whole system is set to ACCEPT_KEYWORDS="~arch", you of course won't have to 
make a /etc/portage/package.keywords file if you wish to use the snapshots, but 
if you want to use the CVS ebuilds you will have to use one. 

Please read the official Gentoo Portage documentation for more precise 
information on Gentoo's package manager and especially the keyword system. Here 
is an example /etc/portage/package.keywords configuration file, which includes 
CVS keywords for the EFL and most applications based on them: 

x11-wm/e -*x11-plugins/e_modules -*x11-misc/engage -*x11-libs/ewl -*x11-
libs/evas -*media-libs/imlib2 -*dev-libs/eet -*dev-db/edb -*x11-libs/ecore -
*media-libs/etox -*media-libs/edje -*dev-libs/embryo -*x11-libs/esmart -*media-
libs/epsilon -*media-libs/epeg -*app-misc/examine -*net-news/erss -*x11-
misc/entrance -*app-misc/evidence -*media-libs/emotion -*media-gfx/elicit -
*media-gfx/entice -*dev-util/e_utils -*dev-libs/engrave -*media-video/eclair -*
If you wish to use the snapshots instead, and are running a stable (arch) 
system, replace the -* with ~arch. For most people (those using Intel 
compatible 32 bit x86 processors) this means ~x86. Note that you should not 
mix -* and ~x86 ebuilds. Another important thing to remember is that you need 
to manually specify the ebuilds in the correct order when you emerge them. This 
is because if you already have E17 installed, running "emerge e" will only 
update the E17 window manager itself, and not the EFL - in which case it'll 
most likely fail to compile. The other reason is because even if you don't have 
E17 installed, Portage will not emerge the libraries in the correct order if 
you simply "emerge e" and let Portage take care of the dependencies. The 
correct build order can be found in the "Building order and CVS notes" (2.1) 
section of this guide. 
If you just want to get all E17 related programs and libraries that are covered 
in this guide, you can use the following emerge line (this will install or 
update in a correct order):

emerge eet dev-db/edb imlib2 evas ecore epeg embryo edje epsilon esmart emotion 
ewl e engrave e_utils e_modules \entice engage entrance evidence eclair etox 
erss elicit
Note that sometimes there may not always be ~arch (snapshot) versions of these 
ebuilds available. The CVS ebuilds (-*) are always available. For those who 
aren't using the ebuilds, you need to specify a certain version of AUTOMAKE and 
AUTOCONF. You can add it to the for example: 

#!/bin/shexport WANT_AUTOCONF=2.5export WANT_AUTOMAKE=1.7
Comment 2 SpanKY gentoo-dev 2005-09-25 14:58:45 UTC
if you're going to use livecvs ebuilds you should be able to figure out that
you're going to have to use livecvs ebuilds for ALL e17 packages