Package Details: enlightenment-git 0.25.99.24774.gc8b1077de-1

Git Clone URL: https://aur.archlinux.org/enlightenment-git.git (read-only, click to copy)
Package Base: enlightenment-git
Description: Enlightenment window manager - Development version
Upstream URL: http://www.enlightenment.org
Licenses: BSD
Conflicts: enlightenment
Provides: enlightenment, notification-daemon
Submitter: Scimmia
Maintainer: raster
Last Packager: raster
Votes: 63
Popularity: 0.000000
First Submitted: 2014-01-08 21:25 (UTC)
Last Updated: 2022-06-13 11:52 (UTC)

Dependencies (28)

Required by (42)

Sources (1)

Latest Comments

raster commented on 2021-05-18 15:56 (UTC)

i know. i don't know why.. it doesn't affect the results though. it doesn't happen with a normal build (outside of makepkg) so some cflag/link flag that pacman is enforcing causes this - or it's strip.

laurent_waro commented on 2021-05-18 15:45 (UTC)

I've got this message when I do an update : readelf: Warning: There is a hole [0xccca5 - 0xcccc7] in .debug_loc section. A lot of this message.

Past install didn't show these messages.

Note that this message appears when I update enlightenment-git and elf-git and terminology-git too.

raster commented on 2021-04-04 09:48 (UTC)

fyoi - this is not the place to discuss upstream bugs really... packaging issues - yes, maybe bringing attention to some arch specific issue, but upstream bug reporting infra (phabricator, email, irc) is the place to be. :)

that aside, seek times or filesystem could impact that too. what is running at the time (before the dialog appears)? efreetd? any other efreet processes? is it that the initial setup of file monitors fails because too many fd's are used and opens begin to fail? have you tried increasing the maximum fd limit for your user? did efreetd_*_cache_create (3 different utilities efreetd spawns on startup to do the scan + update of the cache) crash? i don't know... so much information missing and this forum is going to be slow in finding it. :)

maderios commented on 2021-04-04 09:12 (UTC)

Slow disk? (average) hdparm -Tt /dev/sda /dev/sda: Timing cached reads: 9064 MB in 1.99 seconds = 4546.39 MB/sec Timing buffered disk reads: 330 MB in 3.02 seconds = 109.42 MB/sec

raster commented on 2021-04-03 20:48 (UTC)

is efreetd running? is it busy? this message happen because e doesn't get an update event within its timeout expires. so either things are being super-slow or efreetd keeps crashing and never sends the event etc. - the fact after a restart it's ok tells me this may be due to a slow disk and a lot of file to scan and it just is taking a while...

maderios commented on 2021-04-03 13:40 (UTC)

@laurent_waro Same for me. This is an old issue. https://phab.enlightenment.org/T7045

laurent_waro commented on 2021-04-03 13:26 (UTC)

I've got this message from E : "Efreet did not update cache. Please check your efreet setup. Is effretd running". The directory .cache/efreet is owned by me and is writable.Any ideas to help me to find the origin of this warning? Thanks for the update of E, top!

EndlessEden commented on 2020-10-21 13:36 (UTC)

Request: please add network-manager-applet to optional dependencies, for NetworkManager Support. (NetworkManager is alot more fleshed out than connman)

raster commented on 2020-05-15 23:26 (UTC)

aaah thanks. change of default cflags.... so it was a cflags thing - just a change in compiler cflags built in... got it. fixed upstream in git

andre.vmatos commented on 2020-05-15 16:48 (UTC)

Looks like it's caused by gcc10 defaulting to -fno-common, which fails with the multiple definitions error on linking instead of merging them. I managed to get this package compiled under gcc10 by adding -fcommon to $CFLAGS to revert to the previous behavior

raster commented on 2020-05-15 15:16 (UTC)

oh dear... i heard gcc10 was having issues... now i see. mental note. do NOT upgrade to gcc10... :)

maderios commented on 2020-05-15 10:40 (UTC)

It seems there's a real problem with gcc 10 https://aur.archlinux.org/pkgbase/linux-lts419/ https://aur.archlinux.org/packages/package-query/

maderios commented on 2020-05-15 09:19 (UTC)

I get same codepilot issue now. May be an explanation: i updated my system yesterday, after compiling enlightenment. Gcc was upgraded 9.3.0 -> 10.1.0 I built e successfully with 9.3.0

raster commented on 2020-05-14 23:55 (UTC)

codepilot: then... i'm not sure what is up. probably something with custom CFLAGS? i don't know.. something special on your end seems to be causing this that's different

maderios commented on 2020-05-14 19:32 (UTC)

I just built successfully enlightenment-git with last wayland 1.18.0-2

raster commented on 2020-05-14 13:47 (UTC)

i built this right now without issues... my system is not up to date though (i do not want to update it all the time because that tends to create issues with other things i have to do for work). some change in the wayland tools that auto-generate the wl bindings may have started causing this. perhaps its a bug/break in wayland-scanner (part of the wayland package)?. I'm still on 1.18.0-1. or something special in your CFLAGS?

codepilot commented on 2020-05-14 11:45 (UTC)

Hi, unfortunately I cannot compile enlightenment-git currently, it stops with the following error:

[693/698] Linking target src/modules/wl_desktop_shell.so
FAILED: src/modules/wl_desktop_shell.so 
cc  -o src/modules/wl_desktop_shell.so 'src/modules/9490802@@wl_desktop_shell@sha/meson-generated_xdg-shell-unstable-v6-protocol.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/meson-generated_xdg-shell-protocol.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/meson-generated_input-method-unstable-v1-protocol.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_input_panel.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_wl_shell.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg6.c.o' 'src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg.c.o' -Wl,--as-needed -Wl,--allow-shlib-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,wl_desktop_shell.so -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -g -fvar-tracking-assignments -fdebug-prefix-map=/home/neo/.cache/yay/enlightenment-git/src=/usr/src/debug -fvisibility=hidden -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--unresolved-symbols=ignore-all -lrt -lm -ldl /usr/lib/libeina.so -pthread /usr/lib/libeet.so /usr/lib/libemile.so /usr/lib/libefl.so /usr/lib/libeo.so /usr/lib/libeeze.so /usr/lib/libecore.so /usr/lib/libecore_ipc.so /usr/lib/libecore_file.so /usr/lib/libecore_con.so /usr/lib/libecore_input.so /usr/lib/libecore_input_evas.so /usr/lib/libevas.so /usr/lib/libector.so /usr/lib/libefreet.so /usr/lib/libefreet_mime.so /usr/lib/libeio.so /usr/lib/libeldbus.so /usr/lib/libemotion.so /usr/lib/libelementary.so /usr/lib/libecore_evas.so /usr/lib/libecore_imf.so /usr/lib/libedje.so /usr/lib/libluajit-5.1.so /usr/lib/libefreet_trash.so /usr/lib/libethumb_client.so /usr/lib/libethumb.so /usr/lib/libecore_wl2.so /usr/lib/libefl_canvas_wl.so /usr/lib/libwayland-server.so /usr/lib/libxkbcommon-x11.so /usr/lib/libxkbcommon.so /usr/lib/libwayland-client.so /usr/lib/libuuid.so /usr/lib/libecore_drm2.so /usr/lib/libecore_x.so -Wl,--end-group
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_input_panel.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: multiple definition of `hooks'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_input_panel.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: multiple definition of `xdg_shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_input_panel.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: multiple definition of `shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_wl_shell.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: multiple definition of `shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_wl_shell.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: multiple definition of `hooks'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_wl_shell.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: multiple definition of `xdg_shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg6.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: multiple definition of `xdg_shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg6.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: multiple definition of `hooks'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg6.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: multiple definition of `shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: multiple definition of `xdg_shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:8: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: multiple definition of `hooks'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:9: first defined here
/usr/bin/ld: src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_xdg.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: multiple definition of `shell_resources'; src/modules/9490802@@wl_desktop_shell@sha/wl_desktop_shell_e_mod_main.c.o:/usr/src/debug/enlightenment/build/../src/modules/wl_desktop_shell/e_mod_main.h:7: first defined here
collect2: error: ld returned 1 exit status

raster commented on 2020-05-14 09:28 (UTC)

good point. done. :)

AJSlye commented on 2020-05-14 08:54 (UTC)

The package ccache is not installed by default on most systems. this should probably be added to the makedepends.

stano00 commented on 2020-05-08 15:39 (UTC)

Thanks for your quick response. It built successfully today.

raster commented on 2020-05-08 10:31 (UTC)

it's temporary. i have to put the -beta in the meson package version so it comes out with the tarball. i forgot to commit the previous change thus it worked - (it was local only). the issue is that it's snarfing version from the meson build and the version does indeed have a -beta1 in it... i'll try make the PKGBUILD strip/change this.

stano00 commented on 2020-05-08 03:09 (UTC) (edited on 2020-05-08 03:10 (UTC) by stano00)

I got the following errors when trying to build today. There was no problem building last week.

ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.

ERROR: pkgver() generated an invalid version: 0.24.0-beta1.24074.g27fd81bde

maderios commented on 2019-09-25 19:48 (UTC)

It works now, thanks :)

raster commented on 2019-09-25 17:44 (UTC)

ok. it wasn't kernel or util-linux .. efl removed a -I include cflag from efl-wl and e's build didn't explicitly look for uuid as a dep.

raster commented on 2019-09-25 17:18 (UTC)

Oh... this is new. A kernel update makes this happen. I updated today to 5.3 (from 5.2) and saw this. Couldn't reproduce this before.

maderios commented on 2019-09-24 20:07 (UTC) (edited on 2019-09-24 20:10 (UTC) by maderios)

I got error when compiling enlightenment-git (with last efl-git)

../src/bin/e_gadget_loader.c:8:10: fatal error: uuid.h: No such file or directory 8 | #include <uuid.h> | ^~~~~~~~ compilation terminated. [269/687] Compiling C object 'src/modules/9490802@@pager@sha/pager_gadget_pager.c.o'. ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in build().

raster commented on 2019-08-18 21:18 (UTC)

gestures we do client-side in efl. it's hard to do in x due to the way input systems work in a "global sense". we're improving our touch-friendliness but it needs work and i guess there is a lot to do so ... :)

gothmog123 commented on 2019-08-18 17:38 (UTC)

thanks! any other tips for tablet mode? any way to get touchscreen gestures?

raster commented on 2019-08-18 17:06 (UTC)

we removed it as it wasn;'t maintained really. but you could just load the vkbd module for a virtual keyboard... it does quite a lot for a simple vkbd :)

gothmog123 commented on 2019-08-18 14:03 (UTC)

Hi, sorry, I wanted to use this on a lenovo yoga with the mobile interface but just realized it's been taken out from the first run screen. Is it still available? Compile option?

raster commented on 2017-12-08 00:52 (UTC)

I updated my systems this week and rebuilt efl and enlightenment... and everything "just worked:

==> Finished making: efl-git 1.20.99.56773.gbdcd034af5-1 (Fri Dec  8 09:41:36 KST 2017)
==> Finished making: enlightenment-git 0.22.99.23239.g8f5299be0-1 (Fri Dec  8 09:44:01 KST 2017)

:/ What about your system and mine differ. I also only have the preloadable_libintl.so ... and yet it's not a problem? enlightenment_open here doesn't even link to libintl ... that's why it's not a problem. why is yours linking? libintl support comes from libc here... as it should IMHO. there is no need to link to libintl:

 9:50AM ~ > pacman -Qo /usr/include/libintl.h
/usr/include/libintl.h is owned by glibc 2.26-6

why not on your system?

fredix commented on 2017-12-07 23:27 (UTC)

ok, this workaroud seems to work :

sudo ln -s /usr/lib/preloadable_libintl.so /usr/lib/libintl.so

raster commented on 2017-12-04 08:31 (UTC)

I just rebuilt efl and enlightenment aur pkgs on my arc system... and didn't run into any issues. this may be something new with a "bleeding fresh arch" - maybe a meson or ninja change. i'll have to system update and check. but on a slightly older (a few weeks or so) system it's building.

i update only every few weeks or maybe every 2 or 3 months. i have a whole bunch of arch machines and i like to update them all at once to have them be consistent version-wise, thus i don't update very frequently.

fredix commented on 2017-12-03 14:54 (UTC)

Hi, i can't install enlightenment-git with yaourt because of -lintl :

[205/703] Linking target src/bin/enlightenment_open. FAILED: src/bin/enlightenment_open cc -o src/bin/enlightenment_open 'src/bin/enlightenment_open@exe/e_open.c.o' -Wl,--no-undefined -Wl,--as-needed -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -g -fvar-tracking-assignments -fvisibility=hidden -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group -leina -lpthread -lecore -lefl -lintl -lefreet -lefreet_mime -Wl,--end-group<br> /usr/bin/ld : can not find -lintl

any help ?

raster commented on 2017-11-27 04:31 (UTC)

well it depends on several wayland (or wayland related) deps directly. look at the meson.build: wayland_protocols = dependency('wayland-protocols', version: '>= 1.9') ... dep_wayland = [ dependency('ecore-wl2'), dependency('efl-wl'), dependency('wayland-server' , version: wayland_version), dependency('wayland-client' , version: wayland_version), wayland_protocols, dependency('wayland-scanner', version: wayland_version), dependency('xkbcommon'), dependency('uuid') ] :)

AJSlye commented on 2017-11-27 00:57 (UTC)

Why is this depending on wayland when it already depends on efl-git, which in turn already depends on wayland?

raster commented on 2017-11-07 23:53 (UTC)

yargh! yes. srcinfo. hidden files needing updating... yes. done.

lenoch commented on 2017-11-07 17:35 (UTC)

raster, don't forget to update .SRCINFO once more :-)

TwoD commented on 2017-11-03 08:21 (UTC) (edited on 2017-11-03 08:23 (UTC) by TwoD)

@raster, zmike fixed it back in September: https://phab.enlightenment.org/rEd70ab09a4a769b07527b56332618ab2b9a0326e2 Edit: The above was the commit that broke it (the first time), this one fixed the last issue I had: https://git.enlightenment.org/core/enlightenment.git/commit/?id=b8c5f0c2809c090ace1d8fcdc7ef48ba8eadb893

raster commented on 2017-11-03 05:51 (UTC)

FYI @TwoD -> on latest arch updates i can build with meson. i dont see the problems you do.

raster commented on 2017-11-03 00:08 (UTC) (edited on 2017-11-03 00:08 (UTC) by raster)

You don't have meson.build in the git repo cloned? Your paste log doesn't show any git clone activity etc.... it says its fetching git but no output. Check the git repo clone dir. Something is wrong if you have no meson.build file. I am just building now on arch straight from whatever current git master is (which is what this pkg does) and it builds just fine... have you somehow clones a branch or different repo entirely? I just rebuilt efl and enlightenment AUR git pkgs just fine: $ pacman -Q | grep -- -git efl-git 1.20.99.56150.ge5d1cc731a-1 enlightenment-git 0.22.99.23186.gd4ea0987f-1

ohyash commented on 2017-11-02 18:41 (UTC)

Not sure if it's just me getting this error or everyone.. https://paste2.org/EPY7k1Un

raster commented on 2017-10-27 23:19 (UTC)

done. sorry - i thought i pushed it... but i pushed efl-git ... wrong repo :)

sirus20x6 commented on 2017-10-27 18:09 (UTC)

please fix. Still doesn't build makedepends=('git meson') to makedepends=('git' 'meson')

sirus20x6 commented on 2017-10-25 04:03 (UTC)

@raster well it doesn't build for me. it says it cant satisfy git meson which of course doesn't exist. pretty sure changing: makedepends=('git meson') to makedepends=('git' 'meson') would fix it

raster commented on 2017-10-20 05:49 (UTC)

indeed it should be 'git' and 'meson'. oddly it builds. i still need to look into this new meson issue. i haven't had time this week.

sirus20x6 commented on 2017-10-20 05:29 (UTC)

i think git meson should be git and meson in depends?

raster commented on 2017-10-12 04:42 (UTC)

That's new. I haven't seen that before but my system isn't totally up to date. I'm travelling right now so I don't have time to fix it this week but will look next week.

TwoD commented on 2017-10-11 07:18 (UTC)

Build now fails with: Meson encountered an error in file meson_options.txt, line 1, column 0: Invalid kwargs for option "install-sysactions": "default" May be related to recent updates of the meson package, as it builds on a system with meson 0.42.1-2, but not on one with meson 0.43.0-1 and upgrading the older system makes the build fail with the above message.

raster commented on 2017-10-03 05:12 (UTC)

hmmm unexpected change. fixed now.

AJSlye commented on 2017-10-02 22:01 (UTC) (edited on 2017-10-02 22:03 (UTC) by AJSlye)

build fails with: fatal: remote error: git:// protocol is now deprecated in flavor or https:// : /core/efl.git The source array needs to be changed to: source=("$_pkgname::git+https://git.enlightenment.org/core/$_pkgname.git")

raster commented on 2017-09-17 12:52 (UTC)

indeed correct. it does need meson. interesting it didnt have autotools there as a build dep before either... just git

TwoD commented on 2017-09-17 09:35 (UTC)

Isn't this missing a build dependency on meson?

GavinFernandes commented on 2017-08-23 11:10 (UTC)

See my efl-git comment

raster commented on 2017-08-23 09:32 (UTC)

same as my comment on efl. i can take over. all my machines (arm, x86) run arch. i can maintain...

GavinFernandes commented on 2017-08-23 09:16 (UTC)

Sorry, my laptop is kaput and I'm going to college so I won't have time to maintain the package. Thanks.

AJSlye commented on 2017-08-16 15:00 (UTC)

One more thing. bluez4 no longer exists, you might want to remove it as an optdepends.

GavinFernandes commented on 2017-08-15 09:26 (UTC)

Ok thanks for pointing it out, I've updated the package (and tested it after) making corrections

AJSlye commented on 2017-08-14 02:50 (UTC) (edited on 2017-08-14 02:58 (UTC) by AJSlye)

EFL already depends on wayland and wayland-protocals, enlightenment depends on efl. so why the depends for wayland? Only xorg-server-xwayland should be needed here. Also, how can xorg-server-xwayland be a depends and an optdepends? That makes no sense, shouldn't it be either a depends, or a makedepends and optdepends.

Scimmia commented on 2016-03-28 14:48 (UTC)

Looks like Raster fixed the Elm pc file this morning, so things work again. Updated the dep here.

jabol240 commented on 2016-03-28 14:23 (UTC)

ok thanks will wait and then try again

Scimmia commented on 2016-03-26 20:04 (UTC)

elementary-git is provided by efl-git. I will be changing the dep as soon as they get some things figured out so you can actually build things against the new, merged efl.

jabol240 commented on 2016-03-26 20:02 (UTC)

strangely, it complains about missing elementary-git.

bhundven commented on 2015-11-07 10:17 (UTC)

v0.20.0-beta is out. Lots of updates. And 14 days of updates since that tag. I have an issue with the current version where the screen goes blank, which I think is fixed in 7d2a55f.

Scimmia commented on 2015-09-30 15:42 (UTC)

This package now has Wayland support! Running enlightenment_start directly from a tty (instead of within X) will automatically load the drm module and start a Wayland compositor. Still has a ways to go, but give it a try.

nspaeth commented on 2015-03-05 18:28 (UTC)

Ahh, I just assumed (without looking into it, admittedly) that those flags were for wayland support and had to remove them to get E to start. Thank you, I wasn't aware of the makepkg.conf option.

Scimmia commented on 2015-03-04 23:17 (UTC)

All of the package you mentioned use the "debug" option, so they are built with whatever debug flags you have set in makepkg.conf. By default, that's "-g -fvar-tracking-assignments", but you can make it whatever you want. As for the wayland question, I don't think you understand what it does. It enables wayland clients to run on the X compositor. enlightenment-wayland-git is totally different.

nspaeth commented on 2015-03-04 19:23 (UTC)

Can we have enlightenment-git, elementary-git and efl-git compile with -g and -ggdb3 by default? There are so many bugs that this would ease reporting on. And, so long as there is a separate enlightenment-wayland-git package, how about disabling wayland from *this* package so that the broken state of the wayland implementation doesn't prevent non wayland use.

Scimmia commented on 2014-08-27 04:11 (UTC)

Anyone interested in Wayland support might be interested in https://aur.archlinux.org/packages/enlightenment-wayland-git/ Don't expect everything to work right, and there is no xwayland support, but it runs. Many EFL programs run as well.

commented on 2014-07-20 10:30 (UTC)

Ok, too bad. I'm anxious to try it out, since Enlightenment will include the de facto first Tiling window manager that I know of (via the Tiling 2 module).

Scimmia commented on 2014-07-18 03:12 (UTC)

It is, but it doesn't really work yet.

commented on 2014-07-17 23:08 (UTC)

I have not yet had the time to check it out, but these commits look like xwayland support to me (they have not yet been merged into trunk afaict, though): https://git.enlightenment.org/core/enlightenment.git/log/src?h=devs%2Fdevilhorns%2Fxwayland&qt=grep&q=xwayland

Nierro commented on 2014-03-19 08:43 (UTC)

@munyamunya: So it seems it will take lots of time before it gets someway "usable" (and we still need xwayland support). Good to hear it is starting at least.

munyamunya commented on 2014-03-19 01:51 (UTC)

I've been able to get into desktop, do initial setup and logout (only as root, with ivybridge card). Here are build settings http://pastebin.com/jEtN0P0K (I've also used wayland-git). It is buggy as hell: mouse clicks are almost always ignored, screen updating issues until mouse input, disappearing mouse cursor and overall lagginess. And desktop size was much bigger than my 1680x1050 so I couldn't see the bottom. I have found out that "wrong EGL configuration" errors occur because of gallium-egl in mesa, probably. Hope this helps someone.

Scimmia commented on 2014-03-19 01:16 (UTC)

@Nierro, I've gotten further by removing --enable-wayland-egl and running it as root. It's crashing, though: https://gist.github.com/Scimmia22/9633636. If I don't run as root, I just get input errors like you were.

Nierro commented on 2014-03-18 18:35 (UTC)

Compile went fine but i cannot start enlightenment, here is a log: http://pastie.org/8948285 . Don't know whether it depends on disabling wl_x11 module. I ran enlightenment_start after a clean reboot with no DE previously launched, from a vt. And obviously i exported the 2 variables as written in the blog post.

Scimmia commented on 2014-03-18 17:49 (UTC)

@Nierro, none of the upstream experts are available right now. I'm thinking that the wl_x11 module shouldn't even be built with --enable-wayland-only, can you try it with --disable-wl_x11? It built for me that way, but I don't know about functionality as I'm not even sure what that module is for.

Scimmia commented on 2014-03-18 16:56 (UTC)

Yeah, I'm getting the same thing, I hadn't tested it since wayland doens't work well on my test system. Needs reported upstream.

Nierro commented on 2014-03-18 16:41 (UTC)

I'm getting this error trying to compile enlightenment-git with wayland support: http://pastie.org/8947973 . This is the pkgbuild i'm using: http://pastie.org/8947978 (everything else is the same as yours pkgbuild). Efl-git and elementary-git version: 1.9.99.25006.aad13a2-1 and 1.9.99.9620.cc827fe-1.

Scimmia commented on 2014-03-18 15:47 (UTC)

E is now able to run as a Wayland compositor, as announced in this blog post: http://e19releasemanager.wordpress.com/2014/03/18/by-your-powers-combined/ efl-git now has drm enabled, and has had wayland_shm enabled for a long time now, so you shouldn't have to make any changes there unless you want EGL. If you do, changing '--with-opengl=full' & '--disable-egl' to '--with-opengl=es' & '--enable-egl' will do it. If someone has a good argument for switching away from full opengl by default, I'm all ears. There are a number of changes that need to be made to this package to build for wayland only, the readme quoted in the blog lays them out pretty well.

Scimmia commented on 2014-02-15 15:44 (UTC)

It's already there.

10ne1 commented on 2014-02-15 14:21 (UTC)

You should update the "conflicts" because the stable enlightenment18, not 17 are in the arch repos now

Scimmia commented on 2014-01-20 20:06 (UTC)

This now includes the new packagekit module, please use it with caution. It will update your pacman database to check for updates, so you should never use pacman -S <packagename> if it module reports any packages that need updated. It's better to use pacman -Su <packagename> or pacman -Syu <packagename> to be safe.

Nierro commented on 2014-01-15 14:51 (UTC)

How can i run enlightenment as a wayland compositor?

Scimmia commented on 2014-01-15 05:39 (UTC)

Oh, and make sure to update elementary-git at the same time. I bumped the pkgver on it so that people with automated tools will get both updates.

Scimmia commented on 2014-01-15 05:38 (UTC)

All of the changes Mike has been working on for E19 have just been merged. He recommends backing up your configuration (~/.e/) in case you want to go back to E18 for a while. E19 has a rewrite of the compositor, so the changes behind the scenes are pretty major and require an update to your configuration that cannot be reversed.

highway commented on 2014-01-11 02:36 (UTC)

uninstalled e17-git and the e17-git-debug, installed this, started X . . . easy as pie! thanks for all of the hard work!

Scimmia commented on 2014-01-08 21:27 (UTC)

The rename is on, new package at https://aur.archlinux.org/packages/enlightenment-git/ Everyone should update as soon as possible. This package will be merged with that one.

Scimmia commented on 2014-01-08 21:26 (UTC)

Yes, the pkgver says rc2, they just haven't bothered to update it in the master branch yet. This is the final release of 0.18 + bugfixes.

Nierro commented on 2014-01-05 20:28 (UTC)

Ok, i'll wait that day then. Thank you very much ;)

Scimmia commented on 2014-01-05 17:49 (UTC)

Yes, you still need to specify that branch if you want e19. discomfitor posted on the mailing list last Monday that he only had a couple of issues there that needed to be fixed before he merges it to master and "it's almost definitely going to happen this week". We know how software development goes, it didn't happen last week. I would expect it very soon; when it happens, I'll actually update this package so that the pkgver goes to 0.18.99 to match the other git packages.

Nierro commented on 2014-01-05 14:24 (UTC)

Does this package still needs "#branch=devs/discomfitor/e19" to build e19? I guess it builds e18-git, so what one day will become e19. Is this correct?

Scimmia commented on 2014-01-03 03:00 (UTC)

Yes it should, but until very recently, the "enlightenment" package in [extra] was E16, so naming this enlightenment-git would have been confusing. Since this is the -git version of the enlightenment17 package, that's the name I used. Luckily, Ronald van Haren is fixing the names in [extra] with the E18 release; when that happens, I'll rename this one, too. See: https://bugs.archlinux.org/task/33962

commented on 2014-01-03 02:56 (UTC)

@Scimmia: Sorry if if this has been asked before (couldn't find any such question), but what about the nomenclature of the package? Should the name not change to simply "enlightenment-git" if it follows the master (I have lost the overview of which branch does what for enlightenment, which is why I ask)?

Scimmia commented on 2013-12-26 17:31 (UTC)

@Fedes, no, I'm not. In fact, I can't. The stable release is an update to the enlightenment17 package in the main repos, so creating one here would be a duplicate and against the rules. We need to wait for Ronald van Haren to update it.

Fedes commented on 2013-12-26 17:24 (UTC)

Hey Scimmia, First, let me say thanks for maintining these great packages for one of the best desktops out there, IMO. Are you planning on creating one for E18 stable release? Thanks!

Scimmia commented on 2013-11-25 16:46 (UTC)

For those that just want to follow the alpha/beta releases and not Git HEAD, a PKGBUILD is provided with each tarball. Just extract the tarball, cd into the <new dir>/pkgbuild and run makepkg.

PelPix commented on 2013-11-05 23:54 (UTC)

WAYLAND SUPPORT is what's causing it to crash! I figured it out! Disabled Wayland in E, EFL, and Elementary. Now it boots up without any SEGV's!

Scimmia commented on 2013-09-17 14:31 (UTC)

A bit of shuffling around of conditional and optional deps. Changes upstream required this.

Scimmia commented on 2013-09-15 16:20 (UTC)

I'm hesitant to recommend any specific AUR helper. I use yaourt and it does keep a local copy of VCS repos in /var/abs/local/yaourt, but yaourt has it's own issues. IMO, there is no 'perfect' AUR helper.

Nazfellun commented on 2013-09-01 14:51 (UTC)

Scimmia: Haha, wow, I actually do have the environment variable 'V' set. Builds fine without it :). Thanks for your assistance! Also, unrelated question: do you know of an AUR helper that maintains a persistent local cache of source repositories for VCS-backed AUR packages? Don't like wasting the time+bandwidth using the ones I know of, and building them manually doesn't have much benefit from my point of view.

Scimmia commented on 2013-08-18 17:21 (UTC)

I thought about it, but when I built from that branch, the display was unusable. There have been some bug fixes since then, so it could very well have been fixed by now. AFAIK, none of the deps, build options, or anything else that matters needs changed from this package. Anyone that wants to try E19, all you have to do is add #branch=devs/discomfitor/e19 to the end of the source line, ie: -source=("git://git.enlightenment.org/core/$_pkgname.git") +source=("git://git.enlightenment.org/core/$_pkgname.git#branch=devs/discomfitor/e19")

PelPix commented on 2013-08-18 17:16 (UTC)

It might be a good idea to make a split package, enlightenment19-git, for http://git.enlightenment.org/core/enlightenment.git/log/?h=devs/discomfitor/e19

Scimmia commented on 2013-08-16 03:28 (UTC)

Well Nazfellun, that file looks good, so Autotools isn't the problem. Do you have an environmental variable set for "V"? Looking at how the edje command is constructed, that would explain some things, including why you have verbose build logs. Either that or you've done something with AM_DEFAULT_VERBOSITY, but that doesn't seem to cause the error. Try adding "unset V" before the autogen command and see if anything changes.

Nazfellun commented on 2013-08-15 21:31 (UTC)

@Scimmia: Here's the makefile: http://shados.net/files/Makefile.enlightenment17-git

Scimmia commented on 2013-08-10 04:38 (UTC)

Slight dep update. If you want to use the Wayland client module, you need pixman-git.

Scimmia commented on 2013-08-02 15:59 (UTC)

Could you send me src/modules/Makefile? This can narrow down whether it's an autotools problem or a build time problem. Since the leading "-" on the first parameter is missing as well as '/usr/bin/edje_cc", I'm thinking this has to be the build environment. The one .edj that's being created has the command split into multiple lines, the ones that are failing don't. The one that works is in a different makefile, though, so it's hard to say for sure without seeing them.

Nazfellun commented on 2013-08-02 11:51 (UTC)

Scimmia, yeah, only changed things in makepkg were those and MAKEPKG="-j4". Not sure if there're any other files that'd impact the makepkg build environment. Same issue with default makepkg.conf however, here are the logs: http://www.shados.net/files/default-conf-enlightenment17-git-0.17.99.16958.7cf4bfd-1-x86_64-build.log http://www.shados.net/files/default-conf-enlightenment17-git-0.17.99.16958.7cf4bfd-1-x86_64-package.log

Scimmia commented on 2013-08-02 08:27 (UTC)

Nazfellun, your build environment isn't default, what all have you changed? I'm seeing CFLAGS and DEBUG_CFLAGS at the very least and probably MAKEFLAGS, unless you change some things in the PKGBUILD. What else?

Nazfellun commented on 2013-08-02 05:41 (UTC)

Scimmia, http://www.shados.net/files/enlightenment17-git-0.17.99.16957.e2cf7d3-1-x86_64-build.log http://www.shados.net/files/enlightenment17-git-0.17.99.16957.e2cf7d3-1-x86_64-package.log Like I said, I get errors that result in not building a few .edj files that then can't be installed (specifically e-module-conf2.edj & e-module-tiling.edj).

Scimmia commented on 2013-07-30 15:02 (UTC)

Maribu Thanks for the suggestions, but I don't think they're going to happen. evas_generic_loaders-git is already an optdep of efl-git, so that's covered. Whoever told you that emotion_generic_players is needed is just plain wrong. efl-git is built with the gstreamer engine by default; when that's present, it will be used and the vlc engine will be ignored completely by E.

maribu commented on 2013-07-30 10:32 (UTC)

Hi, there! To get the file manager working properly (with thumbnails) evas_generic_loaders-git is needed. On IRC I also was told that emotion_generic_players-git is also needed (I already got thumbnails of videos after installing evas_generic_loaders-git). Would you like to add these two as optional dependency. Or maybe evas_generic_loaders-git as explicit dependency (it is small and has few explicit dependencies (and a lot of optional dependencies)). Thanks! Regards, Maribu

Scimmia commented on 2013-07-28 05:17 (UTC)

Depends on what you're talking about. It works with Wayland clients (weston-terminal, etc), it does not run on Wayland.

postadelmaga commented on 2013-07-28 01:46 (UTC)

Is it working with wayland ? Anybody gave it a try with wayland/xwayland ?

Scimmia commented on 2013-07-12 13:36 (UTC)

Nazfellun, it's not written to a file by default, but adding the --log switch will do it. If your system uses a non-english locale, please use "LC_ALL=C makepkg --log"

Nazfellun commented on 2013-07-12 08:27 (UTC)

Scimmia: Is the build log written to file anywhere? If not, what's the best way to pastebin it? Sorry for the late response, but the build is still failing for me so at least it's still relevant :P.

Fedes commented on 2013-06-27 17:16 (UTC)

Thanks much Scimmia! BTW, It compiled fine after I re-compiled efl-git :)

Scimmia commented on 2013-06-25 15:55 (UTC)

The "-Syu --aur" caught this package because I uploaded a new version of the PKGBUILD. That only happens when there is something that needs changed, not every time there's an update to the Git repo. I that's yaourt, try "-Syu --aur --devel", it will go through each of your VCS packages and check for updates in the actual code.

Fedes commented on 2013-06-25 15:47 (UTC)

Ahh that might be it, silly me. I'm used to the non-git version :). I will try re-compiling efl-git and let you know. I thought elementary-git and efl-git would be updated with -Syu --aur though, like it happened for this package.

Scimmia commented on 2013-06-24 23:45 (UTC)

The efreet async stuff was just added to EFL at the end of last week. Have you updated efl-git?

Fedes commented on 2013-06-24 21:39 (UTC)

I'm getting a compilation error with latest version, and compilation won't finish: enlightenment-e_int_menus.o: In function `_e_int_menus_apps_thread_new': /tmp/yaourt-tmp-fede/aur-enlightenment17-git/src/enlightenment/src/bin/e_int_menus.c:902: undefined reference to `efreet_menu_async_parse' /tmp/yaourt-tmp-fede/aur-enlightenment17-git/src/enlightenment/src/bin/e_int_menus.c:879: undefined reference to `efreet_menu_async_get' /tmp/yaourt-tmp-fede/aur-enlightenment17-git/src/enlightenment/src/bin/e_int_menus.c:902: undefined reference to `efreet_menu_async_parse' collect2: error: ld returned 1 exit status

Scimmia commented on 2013-06-22 17:48 (UTC)

A few small changes, but the one that triggered the new PKGBUILD was the changing of the udisks dep to udisks2. For anyone that doesn't read the mailing list or the release manager's blog, E18 is now in a feature freeze. If they can get EFL 1.8 out the door, I'm guessing E18 won't be too far behind, although Mike is quoting a release date in the 2023-2025 range right now. :)

Scimmia commented on 2013-05-21 14:07 (UTC)

I took a slightly different tack. This commit: http://git.enlightenment.org/core/enlightenment.git/commit/?id=c0e9dff6ccf9090dd71f856aed483daec55e5c0f Will simply disable the wayland module if your version of wayland-server is too old (build would fail before, which is why I was going to change the dep). Simply put, if you want to use wayland client support, you need wayland-git. If you don't, this will still build fine as-is.

andre.vmatos commented on 2013-05-13 11:25 (UTC)

+1 to wayland-git... this package is intended to be a development version, with latest features, so is wayland-git.

Scimmia commented on 2013-05-13 09:32 (UTC)

Looking for opinions, guys. Devilhorns just updated the wayland code, but it requires wayland from git instead of 1.1.0. Would you guys prefer I just drop wayland client support or change the deps to require wayland-git?

Scimmia commented on 2013-05-08 00:36 (UTC)

eventingmonkey: nope. 0.17.2.1 is a release from a stable branch that only gets bug fixes, this package follows Git master, which is development for the next version, 0.18.0. 0.17.2.1 should be done in the main enlightenment17 package, but Ronald van Haren seems to be MIA. He said he was going to be out of touch for a couple of weeks while moving, but that was nearly two months ago, so I have no idea what's going on.

eventingmonkey commented on 2013-05-07 15:03 (UTC)

Any plans to use version 0.17.2.1?

Scimmia commented on 2013-04-30 06:11 (UTC)

In addition to fixing the versioned dep and adding the short hash to pkgver, I've now enabled Wayland client support. This allows Wayland clients to run within E, it does not allow E to run without X. Raster has asked people not to disable update checking, they use this to get a rough idea of the number of users. If you already disabled it, don't worry about it since there's not an easy way to re-enable it without rerunning the initial setup wizard.

Scimmia commented on 2013-04-27 06:39 (UTC)

Nazfellun, then I'm not sure what's going on. You'll need to pastebin the entire log.

Nazfellun commented on 2013-04-21 14:34 (UTC)

Scimmia: Yeah, I updated everything just prior to attempting the build.

Scimmia commented on 2013-04-17 07:46 (UTC)

Although I would advise waiting on rebuild this, there's a major bug right now that's being worked on.

Scimmia commented on 2013-04-17 07:45 (UTC)

Builds fine here. Basic questions, do you have all of base-devel installed and everything up to date?

Nazfellun commented on 2013-04-17 07:19 (UTC)

When trying to build this, I get the following errors: cannot stat './tiling/e-module-tiling.edj': No such file or directory and cannot stat './tiling/e-module-conf2.edj': No such file or directory As far as I can tell from looking through the build output, it looks like it's not correctly constructing the command to build these files - it attempts to run something like: 'DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC -id ./conf2/images -id ../../data/themes/img conf2/e-module-conf2.edc conf2/e-module-conf2.edj' and gets: '/bin/sh: -DMEDIUMRES_PDA=2: command not found' These look a lot more like the flags passed to a compiler (lacking a leading hyphen) rather than any sort of actual command. Anyone got a solution?

Scimmia commented on 2013-04-05 03:27 (UTC)

This package how now been updated for pacman/makepkg 4.1. It will no longer work with makepkg 4.0.3 or earlier. If you've built this package before, it's best if you remove the existing "src" dir to make sure everything's clean, but it's not required. Either way, the new version will re-download the source. You'll notice that the pkgver has changed significantly. If you're using an AUR helper that tries to check the package version to see if it needs to rebuild, it won't like this so please reinstall this package manually. Going forward, though, this scheme should work much better with those AUR helpers. I could add an epoch to the PKGBUILD, but then we'd be stuck with it forever. Since this should be a one time thing, I think it's better to just ask people to install. I've enabled the new 'debug' option in this PKGBUILD. This will build everything with debugging symbols, then strip them into a separate package. You can choose it install the debugging symbols package or not. If you choose not to install it, I suggest keeping it around so you can install it later if you need meaningful backtraces to track down bugs or file a bug report. The debug compiler flags are defined in makepkg.conf and can be changed to suit your needs.

Scimmia commented on 2013-02-18 15:33 (UTC)

I strongly disagree with that, and defy you to find one instance where a dev (other than yourself) refers to it as "enlightenment18". All of the E17 package releases and the E18 snapshot call it "enlightenment" , versions 0.17.1 and 0.17.99.83478 respectively. The new git repos is called "Enlightenment". If you look at the current official ArchLinux package, it's called enlightenment17-0.17.1-1. You don't think that's redundant and wrong? The reason the pkgver on this package is wrong is because of limitations in the current version of Pacman. I have a pkgver function ready to go for when Pacman 4.1 comes out in a couple of weeks which will correct that, then this package will be named similar to the official package, enlightenment17-svn-0.17.99.82125. Again, wrong, but until the official package switches to "enlightenment", I think I'll stick with it.

T_UNIX commented on 2013-02-18 14:55 (UTC)

Suggestion: Call it like the devs do. There should be no 'enlightenment' or 'enlightenment-git' package. there should be 'enlightenment{16,17}' and 'enlightenment16-svn' and 'enlightenment-17-git' this package should be : enlightenment18-git

Scimmia commented on 2013-02-01 06:15 (UTC)

Yep, they've said for a while now that trunk (which this package uses) is e18, but everyone has used the name e17 for so long, I didn't want to change it and confuse people. So now that they've made it official, the question is, do I change the name of the package to just enlightenment-svn (or rather enlightenment-git after they switch to GIT next week) and potentially have people thinking it's a version of the official enlightenment package, which is e16, instead of the enlightenment17 package? Do I just change the description and leave the name? The official package is going to have to change sometime, I wish they would just go ahead and do it. I've been getting the git packages ready to go, I currently have the pkgdesc set as "Enlightenment window manager (formerly e17) - Development version". Think that's enough?

swiftgeek commented on 2013-02-01 05:18 (UTC)

Isn't it now more like DR18? http://e18releasemanager.wordpress.com/

andre.vmatos commented on 2013-01-15 23:11 (UTC)

Thanks, Scimmia. I deleted and reconfigured. Seems solved. It's a little bit weird, 'cause I'm using almost (as far as I remember) the same configurations and modules I used before (including some extras, like the loved engage), and now CPU use is under 10%. I'll take care of redoing configurations before asking for any issue. Thanks.

Scimmia commented on 2013-01-15 22:09 (UTC)

andre.vmatos, the next things to try would be the two most common troubleshooting steps for Enlightenment. First, remove e-modules-extra, or at least make sure you don't have any of them loaded. They are unsupported 3rd party modules, they have cause plenty of problems in the past. Second, rename or remove your ~/.e and try again. You'll have to redo any configuration you had with this one.

andre.vmatos commented on 2013-01-15 22:01 (UTC)

Hi, Scimmia. I already did, and problem persist. But, apparently, the problem is with efl-svn, not enlightenment17-svn. I installed enlightenment17 from official repos, over efl-svn, and this issue is present too.

Scimmia commented on 2013-01-15 21:56 (UTC)

andre.vmatos, try switching to the OpenGL renderer. Settings > Look > Composite > Engine. The software renderer has some issues right now.

andre.vmatos commented on 2013-01-15 15:03 (UTC)

Hi. I just compiled this package, evas_generic_loaders-svn, elementary-svn, efl-svn and e-modules-extra-svn and I'm experiencing a hard load of CPU. With same configurations and stable packages (from official repos), load on my i5 ivy bridge, without other programs is below 3% in all cores. With SVN packages, 2 cores are constantly over 40%. Someone experiencing this issue?

Scimmia commented on 2013-01-12 03:16 (UTC)

Build order: efl-svn > evas_generic_loaders-svn (optional-recommended) > elementary-svn > enlightenment17-svn

Scimmia commented on 2013-01-04 00:56 (UTC)

e_dbus is no longer required for enlightenment17-svn. If you're going to remove it, you should rebuild this package after doing so, because it will link to e_dbus if it's available.

capoeira commented on 2012-07-11 19:58 (UTC)

also, when did it work for you. it worked a few day ago for me, too. but now the repo packages are too old

capoeira commented on 2012-07-11 19:39 (UTC)

@ultraviolet well it didn't for me, using yaourt and svn packages from repo. it tries to install e-svn before the other

ultraviolet commented on 2012-07-11 19:28 (UTC)

https://aur.archlinux.org/packages.php?ID=56393 <-- This should do everything in the right order. It worked for me.

capoeira commented on 2012-07-11 18:15 (UTC)

those packages also depend on e_dbus-svn eet-svn eeze-svn so it makes sense, since you'll need to include the arche17 builds, to make them build from AUR, too, before the sequence I mentioned below

capoeira commented on 2012-07-11 18:03 (UTC)

so, efreet has to be build from svn before compiling this. but efreet svn only builds building ecore and eina from svn before. ecore only build builing eina from svn before. ecore-evas also edje needs to be build before wich requires embryo and evas to be build before. after building embryo and evas I than had to build ecore once again, because ecore-evas wasn't build the first time, wich is needed by edje so, to build e-svn, the packages have to be build in this order: embryo-svn-arche17 <> evas-svn-arche17 > edje-svn-arche17 > eina-svn-arche17 > ecore-svn-arche17 > efreet-svn-arche17 > e-svn-arche17

capoeira commented on 2012-07-10 19:40 (UTC)

enlightenment-e_intl.o: In function `e_intl_language_set': e_intl.c:(.text+0x16ac): undefined reference to `efreet_lang_reset' collect2: error: ld returned 1 exit status