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 .. 10 11 12 13 14 15 16 17 18 Next › Last »

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?