Package Details: enlightenment-git 0.24.0.beta1.24079.gd63f4a53e-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=0.24.0.beta1.24079.gd63f4a53e, notification-daemon
Submitter: Scimmia
Maintainer: raster
Last Packager: raster
Votes: 64
Popularity: 0.166420
First Submitted: 2014-01-08 21:25
Last Updated: 2020-05-14 09:28

Dependencies (22)

Required by (47)

Sources (1)

Scimmia commented on 2013-05-08 00:36

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

Any plans to use version 0.17.2.1?

Scimmia commented on 2013-04-30 06:11

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

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

andre.vmatos commented on 2013-04-21 20:38

I'm getting high CPU usage on idle (~25% on i5 ivy-bridge) with enlightnement17-git and efl-git. This problem is present for a long time (around 4 months), but I was using stable versions and didn't reported before. Stable versions is around 0-1% in idle, and it's occurs even in an fresh config (removing ~/.e). Any idea or way of debuging this? I'm using only official modules. Thanks

Nazfellun commented on 2013-04-21 14:34

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

Scimmia commented on 2013-04-17 07:46

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

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

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

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.