1 |
Esta es la guia para instalar Enlightenment 0.17 en Gentoo. Si bien está |
2 |
en ingles, no creo que tengas problemas para entenderlo. |
3 |
De todas formas te cuento, que yo he instalado DR17 de dos maneras, una |
4 |
a la manera Gentoo y otras desde cvs |
5 |
(https://vogelweith.homeftp.net/Linux/e17_en.php) |
6 |
Si bien es más tedioso, prefiero hacerlo de esa forma. Lo que sí, |
7 |
respeta el orden de instalación de las librerías y aplicaciones. |
8 |
Una vez instalado, creas un archivos .xinit, en tu /home y dentro de él |
9 |
la siguiente línea: |
10 |
|
11 |
exec /path/al-ejecutable-de-enlightenment |
12 |
|
13 |
No te coloco el path, puesto que varía de acuerdo a la forma de |
14 |
instalación que hayas elegido. |
15 |
Cualquier duda, consultá. |
16 |
|
17 |
Saludos |
18 |
|
19 |
Gentoo: |
20 |
|
21 |
There are ebuilds in Portage for all EFL and most programs that use |
22 |
them. In addition to snapshots that are updated every few weeks, there |
23 |
are also live CVS ebuilds available. This can sometimes change though, |
24 |
sometimes there are only CVS ebuilds available for certain |
25 |
libraries/programs. Check the Gentoo package database to see the current |
26 |
situation. All CVS ebuilds have sudo as a dependency, so it will also be |
27 |
installed if you use the CVS ebuilds. It can be considered to be a |
28 |
security risk. The default sudo config file should not allow much |
29 |
though, so unless you edit it to allow insecure stuff it shouldn't be a |
30 |
problem on normal non mission-critical desktop systems. This is of |
31 |
course a question of opinion so you'll have to decide for yourself if |
32 |
you consider it a risk. Another thing you should know is that the CVS |
33 |
ebuilds obviously don't check md5sums. The CVS ebuilds will also use |
34 |
root for all steps of the installation and may not always work, |
35 |
depending on the current CVS situation. The snapshot ebuilds are only |
36 |
updated if nothing is seriously broken. |
37 |
|
38 |
The CVS ebuilds are marked with the -* keyword while the snapshots are |
39 |
marked ~arch. Obviously neither the snapshots or the CVS ebuilds are |
40 |
marked stable. These ebuilds are maintained by Mike Frysinger |
41 |
(vapier@g.o). If your whole system is set to |
42 |
ACCEPT_KEYWORDS="~arch", you of course won't have to make |
43 |
a /etc/portage/package.keywords file if you wish to use the snapshots, |
44 |
but if you want to use the CVS ebuilds you will have to use one. |
45 |
|
46 |
Please read the official Gentoo Portage documentation for more precise |
47 |
information on Gentoo's package manager and especially the keyword |
48 |
system. Here is an example /etc/portage/package.keywords configuration |
49 |
file, which includes CVS keywords for the EFL and most applications |
50 |
based on them: |
51 |
|
52 |
|
53 |
|
54 |
x11-wm/e -* |
55 |
x11-plugins/e_modules -* |
56 |
x11-misc/engage -* |
57 |
x11-libs/ewl -* |
58 |
x11-libs/evas -* |
59 |
media-libs/imlib2 -* |
60 |
media-libs/imlib2_loaders -* |
61 |
dev-libs/eet -* |
62 |
dev-db/edb -* |
63 |
x11-libs/ecore -* |
64 |
media-libs/etox -* |
65 |
media-libs/edje -* |
66 |
dev-libs/embryo -* |
67 |
x11-libs/esmart -* |
68 |
media-libs/epsilon -* |
69 |
media-libs/epeg -* |
70 |
app-misc/examine -* |
71 |
net-news/erss -* |
72 |
x11-misc/entrance -* |
73 |
app-misc/evidence -* |
74 |
media-libs/emotion -* |
75 |
media-gfx/elicit -* |
76 |
media-gfx/entice -* |
77 |
dev-util/e_utils -* |
78 |
dev-libs/engrave -* |
79 |
media-video/eclair -* |
80 |
|
81 |
|
82 |
If you wish to use the snapshots instead, and are running a stable |
83 |
(arch) system, replace the -* with ~arch. For most people (those using |
84 |
Intel compatible 32 bit x86 processors) this means ~x86. Note that you |
85 |
should not mix -* and ~x86 ebuilds. Another important thing to remember |
86 |
is that you need to manually specify the ebuilds in the correct order |
87 |
when you emerge them. This is because if you already have E17 installed, |
88 |
running "emerge e" will only update the E17 window manager itself, and |
89 |
not the EFL - in which case it'll most likely fail to compile. The other |
90 |
reason is because even if you don't have E17 installed, Portage will not |
91 |
emerge the libraries in the correct order if you simply "emerge e" and |
92 |
let Portage take care of the dependencies. The correct build order can |
93 |
be found in the "Building order and CVS notes" (2.1) section of this |
94 |
guide. |
95 |
|
96 |
|
97 |
|
98 |
If you just want to get all E17 related programs and libraries that are |
99 |
covered in this guide, you can use the following emerge line (this will |
100 |
install or update in a correct order): |
101 |
|
102 |
emerge edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl |
103 |
e engrave e_utils erss entice engage entrance evidence e_modules eclair |
104 |
|
105 |
Note that sometimes there may not always be ~arch (snapshot) versions of |
106 |
these ebuilds available. The CVS ebuilds (-*) are always available. For |
107 |
those who aren't using the ebuilds, you need to specify a certain |
108 |
version of AUTOMAKE and AUTOCONF. You can add it to the autogen.sh for |
109 |
example: |
110 |
|
111 |
|
112 |
#!/bin/sh |
113 |
export WANT_AUTOCONF=2.5 |
114 |
export WANT_AUTOMAKE=1.7 |
115 |
|
116 |
|
117 |
|
118 |
Gentoo: |
119 |
|
120 |
There are ebuilds in Portage for all EFL and most programs that use |
121 |
them. In addition to snapshots that are updated every few weeks, there |
122 |
are also live CVS ebuilds available. This can sometimes change though, |
123 |
sometimes there are only CVS ebuilds available for certain |
124 |
libraries/programs. Check the Gentoo package database to see the current |
125 |
situation. All CVS ebuilds have sudo as a dependency, so it will also be |
126 |
installed if you use the CVS ebuilds. It can be considered to be a |
127 |
security risk. The default sudo config file should not allow much |
128 |
though, so unless you edit it to allow insecure stuff it shouldn't be a |
129 |
problem on normal non mission-critical desktop systems. This is of |
130 |
course a question of opinion so you'll have to decide for yourself if |
131 |
you consider it a risk. Another thing you should know is that the CVS |
132 |
ebuilds obviously don't check md5sums. The CVS ebuilds will also use |
133 |
root for all steps of the installation and may not always work, |
134 |
depending on the current CVS situation. The snapshot ebuilds are only |
135 |
updated if nothing is seriously broken. |
136 |
|
137 |
The CVS ebuilds are marked with the -* keyword while the snapshots are |
138 |
marked ~arch. Obviously neither the snapshots or the CVS ebuilds are |
139 |
marked stable. These ebuilds are maintained by Mike Frysinger |
140 |
(vapier@g.o). If your whole system is set to |
141 |
ACCEPT_KEYWORDS="~arch", you of course won't have to make |
142 |
a /etc/portage/package.keywords file if you wish to use the snapshots, |
143 |
but if you want to use the CVS ebuilds you will have to use one. |
144 |
|
145 |
Please read the official Gentoo Portage documentation for more precise |
146 |
information on Gentoo's package manager and especially the keyword |
147 |
system. Here is an example /etc/portage/package.keywords configuration |
148 |
file, which includes CVS keywords for the EFL and most applications |
149 |
based on them: |
150 |
|
151 |
|
152 |
|
153 |
x11-wm/e -* |
154 |
x11-plugins/e_modules -* |
155 |
x11-misc/engage -* |
156 |
x11-libs/ewl -* |
157 |
x11-libs/evas -* |
158 |
media-libs/imlib2 -* |
159 |
media-libs/imlib2_loaders -* |
160 |
dev-libs/eet -* |
161 |
dev-db/edb -* |
162 |
x11-libs/ecore -* |
163 |
media-libs/etox -* |
164 |
media-libs/edje -* |
165 |
dev-libs/embryo -* |
166 |
x11-libs/esmart -* |
167 |
media-libs/epsilon -* |
168 |
media-libs/epeg -* |
169 |
app-misc/examine -* |
170 |
net-news/erss -* |
171 |
x11-misc/entrance -* |
172 |
app-misc/evidence -* |
173 |
media-libs/emotion -* |
174 |
media-gfx/elicit -* |
175 |
media-gfx/entice -* |
176 |
dev-util/e_utils -* |
177 |
dev-libs/engrave -* |
178 |
media-video/eclair -* |
179 |
|
180 |
|
181 |
If you wish to use the snapshots instead, and are running a stable |
182 |
(arch) system, replace the -* with ~arch. For most people (those using |
183 |
Intel compatible 32 bit x86 processors) this means ~x86. Note that you |
184 |
should not mix -* and ~x86 ebuilds. Another important thing to remember |
185 |
is that you need to manually specify the ebuilds in the correct order |
186 |
when you emerge them. This is because if you already have E17 installed, |
187 |
running "emerge e" will only update the E17 window manager itself, and |
188 |
not the EFL - in which case it'll most likely fail to compile. The other |
189 |
reason is because even if you don't have E17 installed, Portage will not |
190 |
emerge the libraries in the correct order if you simply "emerge e" and |
191 |
let Portage take care of the dependencies. The correct build order can |
192 |
be found in the "Building order and CVS notes" (2.1) section of this |
193 |
guide. |
194 |
|
195 |
|
196 |
|
197 |
If you just want to get all E17 related programs and libraries that are |
198 |
covered in this guide, you can use the following emerge line (this will |
199 |
install or update in a correct order): |
200 |
|
201 |
emerge edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl |
202 |
e engrave e_utils erss entice engage entrance evidence e_modules eclair |
203 |
|
204 |
Note that sometimes there may not always be ~arch (snapshot) versions of |
205 |
these ebuilds available. The CVS ebuilds (-*) are always available. For |
206 |
those who aren't using the ebuilds, you need to specify a certain |
207 |
version of AUTOMAKE and AUTOCONF. You can add it to the autogen.sh for |
208 |
example: |
209 |
|
210 |
|
211 |
#!/bin/sh |
212 |
export WANT_AUTOCONF=2.5 |
213 |
export WANT_AUTOMAKE=1.7 |
214 |
|
215 |
|
216 |
Gentoo: |
217 |
|
218 |
There are ebuilds in Portage for all EFL and most programs that use |
219 |
them. In addition to snapshots that are updated every few weeks, there |
220 |
are also live CVS ebuilds available. This can sometimes change though, |
221 |
sometimes there are only CVS ebuilds available for certain |
222 |
libraries/programs. Check the Gentoo package database to see the current |
223 |
situation. All CVS ebuilds have sudo as a dependency, so it will also be |
224 |
installed if you use the CVS ebuilds. It can be considered to be a |
225 |
security risk. The default sudo config file should not allow much |
226 |
though, so unless you edit it to allow insecure stuff it shouldn't be a |
227 |
problem on normal non mission-critical desktop systems. This is of |
228 |
course a question of opinion so you'll have to decide for yourself if |
229 |
you consider it a risk. Another thing you should know is that the CVS |
230 |
ebuilds obviously don't check md5sums. The CVS ebuilds will also use |
231 |
root for all steps of the installation and may not always work, |
232 |
depending on the current CVS situation. The snapshot ebuilds are only |
233 |
updated if nothing is seriously broken. |
234 |
|
235 |
The CVS ebuilds are marked with the -* keyword while the snapshots are |
236 |
marked ~arch. Obviously neither the snapshots or the CVS ebuilds are |
237 |
marked stable. These ebuilds are maintained by Mike Frysinger |
238 |
(vapier@g.o). If your whole system is set to |
239 |
ACCEPT_KEYWORDS="~arch", you of course won't have to make |
240 |
a /etc/portage/package.keywords file if you wish to use the snapshots, |
241 |
but if you want to use the CVS ebuilds you will have to use one. |
242 |
|
243 |
Please read the official Gentoo Portage documentation for more precise |
244 |
information on Gentoo's package manager and especially the keyword |
245 |
system. Here is an example /etc/portage/package.keywords configuration |
246 |
file, which includes CVS keywords for the EFL and most applications |
247 |
based on them: |
248 |
|
249 |
|
250 |
|
251 |
x11-wm/e -* |
252 |
x11-plugins/e_modules -* |
253 |
x11-misc/engage -* |
254 |
x11-libs/ewl -* |
255 |
x11-libs/evas -* |
256 |
media-libs/imlib2 -* |
257 |
media-libs/imlib2_loaders -* |
258 |
dev-libs/eet -* |
259 |
dev-db/edb -* |
260 |
x11-libs/ecore -* |
261 |
media-libs/etox -* |
262 |
media-libs/edje -* |
263 |
dev-libs/embryo -* |
264 |
x11-libs/esmart -* |
265 |
media-libs/epsilon -* |
266 |
media-libs/epeg -* |
267 |
app-misc/examine -* |
268 |
net-news/erss -* |
269 |
x11-misc/entrance -* |
270 |
app-misc/evidence -* |
271 |
media-libs/emotion -* |
272 |
media-gfx/elicit -* |
273 |
media-gfx/entice -* |
274 |
dev-util/e_utils -* |
275 |
dev-libs/engrave -* |
276 |
media-video/eclair -* |
277 |
|
278 |
|
279 |
If you wish to use the snapshots instead, and are running a stable |
280 |
(arch) system, replace the -* with ~arch. For most people (those using |
281 |
Intel compatible 32 bit x86 processors) this means ~x86. Note that you |
282 |
should not mix -* and ~x86 ebuilds. Another important thing to remember |
283 |
is that you need to manually specify the ebuilds in the correct order |
284 |
when you emerge them. This is because if you already have E17 installed, |
285 |
running "emerge e" will only update the E17 window manager itself, and |
286 |
not the EFL - in which case it'll most likely fail to compile. The other |
287 |
reason is because even if you don't have E17 installed, Portage will not |
288 |
emerge the libraries in the correct order if you simply "emerge e" and |
289 |
let Portage take care of the dependencies. The correct build order can |
290 |
be found in the "Building order and CVS notes" (2.1) section of this |
291 |
guide. |
292 |
|
293 |
If you just want to get all E17 related programs and libraries that are |
294 |
covered in this guide, you can use the following emerge line (this will |
295 |
install or update in a correct order): |
296 |
|
297 |
emerge edb eet imlib2 imlib2_loaders evas ecore epeg epsilon embryo edje esmart emotion etox ewl |
298 |
e engrave e_utils erss entice engage entrance evidence e_modules eclair |
299 |
|
300 |
Note that sometimes there may not always be ~arch (snapshot) versions of |
301 |
these ebuilds available. The CVS ebuilds (-*) are always available. For |
302 |
those who aren't using the ebuilds, you need to specify a certain |
303 |
version of AUTOMAKE and AUTOCONF. You can add it to the autogen.sh for |
304 |
example: |
305 |
|
306 |
|
307 |
#!/bin/sh |
308 |
export WANT_AUTOCONF=2.5 |
309 |
export WANT_AUTOMAKE=1.7 |
310 |
|
311 |
|
312 |
On Sat, 2005-06-04 at 21:26 +0000, José Zamora wrote: |
313 |
> Saludos. |
314 |
> |
315 |
> El presente email es para saber si algunos de ustedes me da una idea. |
316 |
> Estoy tratando de instalar la versión de Enlightenment 0.17. Mi versión |
317 |
> de gentoo es la versión 2005.0. |
318 |
> |
319 |
> Lo que he realizado hasta ahora es lo siguiente: |
320 |
> |
321 |
> #echo "x11-wm/e -*" >> /etc/portage/package.keywords |
322 |
> #emerge e |
323 |
> |
324 |
> Lo cual me instala 7 paquetes aproximandamente sin ningún tipo de |
325 |
> problemas. Pero al momento de compilar el Enlightenment me cae la |
326 |
> compilación :-( con el siguiente error. |
327 |
> |
328 |
> e_border.h:131: error: parse error before "Ecore_X_Gravity" |
329 |
> e_border.h:131: warning: no semicolon at end of struct or union |
330 |
> e_border.h:131: warning: no semicolon at end of struct or union |
331 |
> e_border.h:151: error: parse error before "Ecore_X_MWM_Hint_Func" |
332 |
> e_border.h:151: warning: no semicolon at end of struct or union |
333 |
> e_border.h:152: warning: data definition has no type or storage class |
334 |
> e_border.h:153: error: parse error before "input" |
335 |
> e_border.h:153: warning: data definition has no type or storage class |
336 |
> e_border.h:154: error: parse error before ':' token |
337 |
> e_border.h:155: error: parse error before ':' token |
338 |
> e_border.h:159: error: parse error before '}' token |
339 |
> e_border.h:159: warning: data definition has no type or storage class |
340 |
> e_border.h:228: error: parse error before "initial_attributes" |
341 |
> e_border.h:228: warning: data definition has no type or storage class |
342 |
> e_border.h:229: warning: data definition has no type or storage class |
343 |
> e_border.h:233: error: parse error before ':' token |
344 |
> e_border.h:234: error: parse error before ':' token |
345 |
> e_border.h:235: error: parse error before ':' token |
346 |
> e_border.h:236: error: parse error before ':' token |
347 |
> e_border.h:237: error: parse error before ':' token |
348 |
> e_border.h:238: error: parse error before ':' token |
349 |
> e_border.h:239: error: parse error before ':' token |
350 |
> e_border.h:240: error: parse error before ':' token |
351 |
> e_border.h:241: error: parse error before ':' token |
352 |
> e_border.h:242: error: parse error before ':' token |
353 |
> e_border.h:243: error: parse error before ':' token |
354 |
> e_border.h:244: error: parse error before ':' token |
355 |
> e_border.h:245: error: parse error before ':' token |
356 |
> e_border.h:246: error: parse error before ':' token |
357 |
> e_border.h:247: error: parse error before ':' token |
358 |
> e_border.h:248: error: parse error before ':' token |
359 |
> e_border.h:249: error: parse error before ':' token |
360 |
> e_border.h:250: error: parse error before ':' token |
361 |
> e_border.h:252: error: parse error before ':' token |
362 |
> e_border.h:266: error: parse error before "Ecore_Animator" |
363 |
> e_border.h:266: warning: no semicolon at end of struct or union |
364 |
> e_border.h:267: warning: data definition has no type or storage class |
365 |
> e_border.h:297: error: parse error before '}' token |
366 |
> In file included from e_includes.h:22, |
367 |
> from e.h:79, |
368 |
> from e_main.c:4: |
369 |
> e_apps.h:48: error: parse error before "Ecore_File_Monitor" |
370 |
> e_apps.h:48: warning: no semicolon at end of struct or union |
371 |
> e_apps.h:50: error: parse error before ':' token |
372 |
> e_apps.h:51: error: parse error before ':' token |
373 |
> e_apps.h:52: error: parse error before ':' token |
374 |
> e_apps.h:54: error: parse error before ':' token |
375 |
> e_apps.h:56: error: parse error before ':' token |
376 |
> In file included from e_includes.h:30, |
377 |
> from e.h:79, |
378 |
> from e_main.c:4: |
379 |
> e_hints.h:24: error: parse error before "Ecore_X_Window_State_Action" |
380 |
> e_main.c: In function `main': |
381 |
> e_main.c:260: error: `ECORE_EVAS_ENGINE_SOFTWARE_X11' undeclared (first |
382 |
> use in this function) |
383 |
> e_main.c:260: error: (Each undeclared identifier is reported only once |
384 |
> e_main.c:260: error: for each function it appears in.) |
385 |
> e_main.c:275: error: `ecore_file_shutdown' undeclared (first use in this |
386 |
> function) |
387 |
> make[3]: *** [e_user.o] Error 1 |
388 |
> make[3]: *** Waiting for unfinished jobs.... |
389 |
> make[3]: *** [e_main.o] Error 1 |
390 |
> make[3]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/src/bin' |
391 |
> make[2]: *** [all-recursive] Error 1 |
392 |
> make[2]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/src' |
393 |
> make[1]: *** [all-recursive] Error 1 |
394 |
> make[1]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e' |
395 |
> make: *** [all] Error 2 |
396 |
> * This is a LIVE CVS ebuild. |
397 |
> * That means there are NO promises it will work. |
398 |
> * If it fails to build, FIX THE CODE YOURSELF |
399 |
> * before reporting any issues. |
400 |
> |
401 |
> !!! ERROR: x11-wm/e-9999 failed. |
402 |
> !!! Function enlightenment_die, Line 73, Exitcode 0 |
403 |
> !!! emake failed |
404 |
> !!! SEND BUG REPORTS TO vapier@g.o NOT THE E TEAM |
405 |
> !!! If you need support, post the topmost build error, NOT this status |
406 |
> message. |
407 |
> |
408 |
> |
409 |
> Gracias por las ideas que puedan aportarme .. |
410 |
> |
411 |
> José |
412 |
> |
413 |
|
414 |
|
415 |
-- |
416 |
gentoo-user-es@g.o mailing list |