Updated 27 February 2011.
This install of e17 does not conflict with the version of Enlightenment DR-16 found on the Debian repositories. It also installs the latest & greatest version from the SVN. But it is not for the timid. There are two ways to go, but both start the same.
NOTE: All instructions assume that you know how to install based on your user/root preference.
Step 1: There are some dependences for installing e17 on debian, from http://www.enlightenment.org/p.php?p=download&l=en.
The folloing list is old, but I keep it handy just in case.
From the command line, cd to where you want to download e17. Where you put it is up to you, my suggestion though is if you are only testing this out, put it in /opt (that's what it is there for). Now to get e17 source code with;
svn co http://svn.enlightenment.org/svn/e/trunk/eina eina
svn co http://svn.enlightenment.org/svn/e/trunk/eet eet
svn co http://svn.enlightenment.org/svn/e/trunk/evas evas
svn co http://svn.enlightenment.org/svn/e/trunk/ecore ecore
svn co http://svn.enlightenment.org/svn/e/trunk/efreet efreet
svn co http://svn.enlightenment.org/svn/e/trunk/embryo embryo
svn co http://svn.enlightenment.org/svn/e/trunk/edje edje
svn co http://svn.enlightenment.org/svn/e/trunk/e_dbus e_dbus
svn co http://svn.enlightenment.org/svn/e/trunk/e e
Once it is finished downloading the fun begins. Each library needs to be built & installed, then the same for the apps. Here is the library build order for debian stable as of 02 Mar 09.
There are additional libraries, but they are not needed initonally. They need to be downloaded the same as the ones abofe, edited to match of course. This is the build order as of 05 Jan 08.
At this point e17 can be installed & ran.
In order to just get the e17 window manager one can stop here.
The following blue text may be depreciated:
There are also additional appliactions on offer from Enlightenment, now would be the time to install them (we are not going to at this juncture). Some of the following may no longer work. If you find one, let me know over to Cloudy Wizzards forum & I'll remove it.Use " svn co http://svn.enlightenment.org/svn/e/trunk/OLD/* * " to download the following.
The following are in " svn co http://svn.enlightenment.org/svn/e/trunk/PROTO/* * "
The next thing to add are the modules. This is the module build order as of 02 Mar 09, build just the ones needed/want.
Now comes the fun part, each library needs to be configured & installed before the next (or in some particular order). After the libraries are installed, then the various & sundry applications are to be built, followed by the the modules. If this is being done from a gui, then cutting & pasting is not a problem. Say though this is being done without a gui then I would suggest getting "gpm - General Purpose Mouse Interface", cuts down on the typos.
Now to the actual building part. CD into each folder & then type;
./autogen.sh && make && make install
The default directory for the install is "/usr/local". The debian way to install stuff is of course to /usr, which is fine if one plans to keep e17 for a spell. If that is the case then add "--prefix=/usr" to ./autogen.sh to install to "/usr/(bin, etc, include, lib, local, sbin, share). On the other hand if this is just to test things out, then again I suggest using "/opt".
Now have at it.
Step 4: Booting into e17.
Well I'm not going to tell an experienced debian user how to login to their system, but the command to start e17 is "enlightenment_start". Any standard window display manager (KDM, GDM, XDM & WDM) should pick up e17 automaticlly, if not then one needs to configure their window display manager of choice by hand. E17 does come with it's own window display manager called Entrance. And last but not least, command line & startx or no window display manager at all.
There are two basic errors one will encounter during the build process.
The first is building stuff out of order. This usually happens during the "make" phase of the build. One can sort this out by reading the error message. They usually say something to the affect of, "can not find <some_*.h_file>" or"<some_file> is missing.
The second error tends to be that something is missing. Which will happen during the ./autogen phase of the build. The error is pretty clear on what is missing, so just get said missing file and go again. If said missing file is already installed & it is the correct version, then try said file-dev or said file-lib.
There is another error that happens from time to time, but
it's not user error. Sometimes the stuff coming from the cvs
is just plane broke, e17 is in the development phase after all.
Just try again later (most times things are fixed in a day or
two, but sometimes can take up to a fortnight