Re: [gentoo-user-es] Enlightenment 0.17

[Apocalypse Now]

Esta es la guia para instalar Enlightenment 0.17 en Gentoo. Si bien está
en ingles, no creo que tengas problemas para entenderlo. 
De todas formas te cuento, que yo he instalado DR17 de dos maneras, una
a la manera Gentoo y otras desde cvs
(https://vogelweith.homeftp.net/Linux/e17_en.php)
Si bien es más tedioso, prefiero hacerlo de esa forma. Lo que sí,
respeta el orden de instalación de las librerías y aplicaciones.
Una vez instalado, creas un archivos .xinit, en tu /home y dentro de él
la siguiente línea:

exec /path/al-ejecutable-de-enlightenment

No te coloco el path, puesto que varía de acuerdo a la forma de
instalación que hayas elegido.
Cualquier duda, consultá.

Saludos

Gentoo:

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
(vapier@g.o). 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 -*
media-libs/imlib2_loaders -*
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 edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl
e engrave e_utils erss entice engage entrance evidence e_modules eclair

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 autogen.sh for
example: 


#!/bin/sh
export WANT_AUTOCONF=2.5
export WANT_AUTOMAKE=1.7
      


Gentoo:

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
(vapier@g.o). 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 -*
media-libs/imlib2_loaders -*
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 edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl
e engrave e_utils erss entice engage entrance evidence e_modules eclair

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 autogen.sh for
example: 


#!/bin/sh
export WANT_AUTOCONF=2.5
export WANT_AUTOMAKE=1.7
      

Gentoo:

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
(vapier@g.o). 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 -*
media-libs/imlib2_loaders -*
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 edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl
e engrave e_utils erss entice engage entrance evidence e_modules eclair

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 autogen.sh for
example: 


#!/bin/sh
export WANT_AUTOCONF=2.5
export WANT_AUTOMAKE=1.7
      

On Sat, 2005-06-04 at 21:26 +0000, José Zamora wrote:
> Saludos.
>
> El presente email es para saber si algunos de ustedes me da una idea.
> Estoy tratando de instalar la versión de Enlightenment 0.17. Mi versión
> de gentoo es la versión 2005.0.
>
> Lo que he realizado hasta ahora es lo siguiente:
>
> #echo "x11-wm/e -*" >> /etc/portage/package.keywords
> #emerge e
>
> Lo cual me instala 7 paquetes aproximandamente sin ningún tipo de
> problemas. Pero al momento de compilar el Enlightenment me cae la
> compilación :-( con el siguiente error.
>
> e_border.h:131: error: parse error before "Ecore_X_Gravity"
> e_border.h:131: warning: no semicolon at end of struct or union
> e_border.h:131: warning: no semicolon at end of struct or union
> e_border.h:151: error: parse error before "Ecore_X_MWM_Hint_Func"
> e_border.h:151: warning: no semicolon at end of struct or union
> e_border.h:152: warning: data definition has no type or storage class
> e_border.h:153: error: parse error before "input"
> e_border.h:153: warning: data definition has no type or storage class
> e_border.h:154: error: parse error before ':' token
> e_border.h:155: error: parse error before ':' token
> e_border.h:159: error: parse error before '}' token
> e_border.h:159: warning: data definition has no type or storage class
> e_border.h:228: error: parse error before "initial_attributes"
> e_border.h:228: warning: data definition has no type or storage class
> e_border.h:229: warning: data definition has no type or storage class
> e_border.h:233: error: parse error before ':' token
> e_border.h:234: error: parse error before ':' token
> e_border.h:235: error: parse error before ':' token
> e_border.h:236: error: parse error before ':' token
> e_border.h:237: error: parse error before ':' token
> e_border.h:238: error: parse error before ':' token
> e_border.h:239: error: parse error before ':' token
> e_border.h:240: error: parse error before ':' token
> e_border.h:241: error: parse error before ':' token
> e_border.h:242: error: parse error before ':' token
> e_border.h:243: error: parse error before ':' token
> e_border.h:244: error: parse error before ':' token
> e_border.h:245: error: parse error before ':' token
> e_border.h:246: error: parse error before ':' token
> e_border.h:247: error: parse error before ':' token
> e_border.h:248: error: parse error before ':' token
> e_border.h:249: error: parse error before ':' token
> e_border.h:250: error: parse error before ':' token
> e_border.h:252: error: parse error before ':' token
> e_border.h:266: error: parse error before "Ecore_Animator"
> e_border.h:266: warning: no semicolon at end of struct or union
> e_border.h:267: warning: data definition has no type or storage class
> e_border.h:297: error: parse error before '}' token
> In file included from e_includes.h:22,
>                  from e.h:79,
>                  from e_main.c:4:
> e_apps.h:48: error: parse error before "Ecore_File_Monitor"
> e_apps.h:48: warning: no semicolon at end of struct or union
> e_apps.h:50: error: parse error before ':' token
> e_apps.h:51: error: parse error before ':' token
> e_apps.h:52: error: parse error before ':' token
> e_apps.h:54: error: parse error before ':' token
> e_apps.h:56: error: parse error before ':' token
> In file included from e_includes.h:30,
>                  from e.h:79,
>                  from e_main.c:4:
> e_hints.h:24: error: parse error before "Ecore_X_Window_State_Action"
> e_main.c: In function `main':
> e_main.c:260: error: `ECORE_EVAS_ENGINE_SOFTWARE_X11' undeclared (first
> use in this function)
> e_main.c:260: error: (Each undeclared identifier is reported only once
> e_main.c:260: error: for each function it appears in.)
> e_main.c:275: error: `ecore_file_shutdown' undeclared (first use in this
> function)
> make[3]: *** [e_user.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[3]: *** [e_main.o] Error 1
> make[3]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/src/bin'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e'
> make: *** [all] Error 2
>  * 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.
>
> !!! ERROR: x11-wm/e-9999 failed.
> !!! Function enlightenment_die, Line 73, Exitcode 0
> !!! emake failed
> !!! SEND BUG REPORTS TO vapier@g.o NOT THE E TEAM
> !!! If you need support, post the topmost build error, NOT this status
> message.
>
>
> Gracias por las ideas que puedan aportarme ..
>
> José
>


-- 
gentoo-user-es@g.o mailing list