AUR (en) - enlightenment-git

Search Criteria

Package Details: enlightenment-git 0.26.99.25007.g044149406-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:	64
Popularity:	0.27
First Submitted:	2014-01-08 21:25 (UTC)
Last Updated:	2024-12-14 20:35 (UTC)

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:

Popularity:

0.27

First Submitted:

2014-01-08 21:25 (UTC)

Last Updated:

2024-12-14 20:35 (UTC)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 Next › Last »

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.