On Monday 25 September 2006 16:26, Helmut Jarausch wrote:
> Hi
>
> how can I unmask a cvs version of a package
>
> I'd like to build
> x11-wm/enlightenment-0.16.9999

As a *very* happy e17 user I can give you some tips. This is a 
longish reply, hopefully  it'll save you some of the mistakes I 
made :-)

I had endless hassles with the enlightenment-0.16.9999 snapshots 
a while back - not everything was always available as a 
snapshot and other miscellaneous issues. But that's not 
important - what is is that I switched to e-9999 (the current 
CVS, not snapshots) and everything works like a dream. I update 
at least weekly and for two months now I've had no breakages 
(not bad for current cvs stuff). The best docs are at get-e (I 
don't have the url handy, but visit www.enlightenment.org and 
the link is near the bottom of the left panel). There you will 
find e17 and efl user guides with gentoo sections contributed 
by vapier. Read that for the full info. I'll give you the short 
version, snipped out of my local copy of the faqs:

****************

To install just the window manager:
(Note: the ebuilds do not resolve all dependencies reliably. You 
have to remerge all packages each time you want to update e17).
Add these to /etc/portage/package.keywords:

x11-wm/e -*
x11-libs/evas -*
dev-libs/eet -*
x11-libs/ecore -*
media-libs/edje -*
dev-libs/embryo -* to 

Then run 

emerge eet evas ecore embryo edje e

and update your x startup scripts/display manager to run the 
enlightenment-0.17 binary

******************

To install the full efl and everything else that comes with it 
(do this instead of the above, not in addition to it):

Add these to /etc/portage/package.keywords:
x11-wm/e -*
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-libs/engrave -*
media-video/eclair -*

then run:

emerge eet dev-db/edb imlib2 evas ecore epeg embryo edje epsilon 
esmart emotion ewl engrave

*****************

These emerge commands will download the latest cvs and emerge 
the packages in the correct order. Don't try and change the 
order in future updates, this breaks stuff :-) Always remerge 
everything. It takes about 45 minutes to do the whole lot on my 
reasonable speedy laptop

The x11-plugins/e_modules ebuild is currently broken as several 
modules don't compile - raster dropped the gadman code in the 
module system and replaced it with something new (gadcon). 
e_modules is mostly 3rd party stiff and not all of it is 
updated yet. The other standard modules, those included with 
the wm itself, all work just fine. These are the ones that are 
broken in e_modules:

bling, calendar, devian, engage, evolume, mbar, monitor, mount 
and rss.
You can either write your own ebuild for the remaining modules 
that work, or copy /usr/portage/distfiles/cvs-src/e_modules 
somewhere and run ./autogen.sh && make && make install in each 
sub-directory. Done as a user it installs the modules to 
~/.e/e/modules/<module_name>/. As root they go 
in /usr/lib/enlightenment/<module_name>/

You might find it more convenient (as I do) to download the cvs 
once and then experiment with compile options without having to 
be online and connect to the cvs server with every emerge:

cvs -d:pserver:[EMAIL PROTECTED]:/var/cvs/e 
login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/var/cvs/e 
co *

Do subsequent emerges like this:
ECVS_SERVER="offline" emerge ....
This will skip the CVS checkout step and just use the local copy 
as is. I'm sure there's a better way to do this, I'm just too 
lazy to find it out.

This will download *everything* related to e for your 
compilation pleasure :-) Not everything has an ebuild and not 
all of it compiles. Once you get e17 running do yourself a big 
favour and emerge evidence, then edit /etc/rc.conf 
appropriately and run /etc/init.d/xdm restart. Do this just 
once and I promise you, you will likely never want to see 
standard xdm/gdm/kdm on your personal machine ever again :-)

share and enjoy :-)

alan
-- 
gentoo-user@gentoo.org mailing list

Reply via email to