Package Details: efl-git 1.27.99.67082.g6860883e18-1

Git Clone URL: https://aur.archlinux.org/efl-git.git (read-only, click to copy)
Package Base: efl-git
Description: Enlightenment Foundation Libraries - Development version
Upstream URL: http://www.enlightenment.org
Licenses: GPL2, custom, BSD, MIT, LGPL2.1
Conflicts: efl, elementary, elementary-git, elementary_test, elementary_test-git, evas_generic_loaders, evas_generic_loaders-git
Provides: efl, elementary, elementary-git, evas_generic_loaders
Submitter: Scimmia
Maintainer: raster
Last Packager: raster
Votes: 88
Popularity: 0.29
First Submitted: 2013-02-15 10:00 (UTC)
Last Updated: 2024-08-07 08:07 (UTC)

Required by (29)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 37 Next › Last »

Scimmia commented on 2013-01-03 21:07 (UTC)

I sent a patch upstream about the build issue.

xangelux commented on 2013-01-03 17:52 (UTC)

Doesn't build because an obsolete macro in the configure.ac, to build change it as the warning says and include de conflicts array to be able to install

Scimmia commented on 2013-01-03 13:09 (UTC)

I really try to only update the PKGBUILD when there's a necessary change. You want me to put a version number on it that won't work with the rest of the PKGBUILD? That doesn't make much sense. If it doesn't work with --holdver, the PKGBUILD is broken IMO. If I say that edbus is provided, but put use a revision number from before the edbus merge, not only is it confusing but it could cause problems if people try to use that revision. I assume you're asking because you use an AUR helper that sees the new version and wants to update it. If you can just grit your teeth and bear it for a while, it'll get better. It will calm down a LOT once they finish the EFL merge. Only 5 libs to go. As for the build order, it's mostly for people building for the first time. Once you have everything built and installed, it doesn't matter except in rare cases that can be dealt with easily as they come up. If you want to know, though, it should be obvious by the fact that the package that has been merged has a warning in the comments, no longer builds, and is marked out of date. Again, this will be much less of an issue when the merge is finally finished. There will only be 4 items in the build order.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 37 Next › Last »