Package Details: efl-git 1.23.99.64945.g8ec6e28b7c-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=1.23.99.64945.g8ec6e28b7c, elementary=1.23.99.64945.g8ec6e28b7c, elementary-git=1.23.99.64945.g8ec6e28b7c, evas_generic_loaders=1.23.99.64945.g8ec6e28b7c
Submitter: Scimmia
Maintainer: raster
Last Packager: raster
Votes: 87
Popularity: 0.054589
First Submitted: 2013-02-15 10:00
Last Updated: 2020-01-28 08:35

Dependencies (59)

Required by (57)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

christoph.gysin commented on 2017-10-02 21:07

sources should be updated, it currently fails with:
fatal: remote error: git:// protocol is now deprecated in flavor or https:// : /core/efl.git


raster commented on 2017-09-02 14:12

You're right. that also needs updating.

AJSlye commented on 2017-09-02 03:31

Shouldn't the openjpeg dependency be openjpeg2 now?
AFAIK, the last remaining bits have been ported.

raster commented on 2017-09-02 01:10

Indeed it does need that. I have local changes that do just that to the PKGBUILD ... BUT there is a problem. Nvidia drivers on X11 have very poor performance (drops from smooth 60fps to 30 or 20 fps or even less). I don't know exactly why. the GLX back-end is sliky smooth. Both GLX and EGL are silky smooth on mesa. So I fix one issue only to create another issue for other people if I enable EGL/gles as it stands right now. I currently don't have a solution, but as soon as I do I'll enable EGL/gles. This thing has to be addressed upstream, but unfortunately it's not the highest priority thing.

timofonic commented on 2017-09-01 16:53

ApBBB | timofonic: efl-git from aur needs --enable-gl-drm to be added and --enable-egl --with-opengl=es
ApBBB | the repo package needs only --enable-gl-drm

PS: If there are other people wanting to maintain the E AUR packages, there's the
possibility to have co-maintainers. It's a not so known feature of AUR, but a very useful one. (I did read this has been mentioned before)

raster commented on 2017-08-23 23:42

no offense taken... :) all good. i'm just happy to help people out and since you can't maintain these anymore - i'm happy to jump in. i just needed the pointer to "adopt"... we do things differently upstream so i was looking for equivalents.

i'll "fix up" the PKGBUILD including maintainer/contributor list soon. as soon as i resolve what to do about the slowness on nvidia+egl/gles (glx+opengl full is just fine, and all mesa drivers are fine either way).

GavinFernandes commented on 2017-08-23 15:20

Yeah it's probably ssh: sorry XP, and don't take offense if I was explaining too deliberately, I just wanted to be maximally clear. And ohh yeah change the first line so that it says I'm a contributor instead of maintainer, and add your name as a maintainer following the format, for both your new packages, and Good Luck! Adiós.

raster commented on 2017-08-23 14:39

aaah the adopt! that's all i needed. the rest is easy (git committing/pushing doing builds, editing and maintaining the pkgbuild) :)

but wait wait... shouldnt it be the one with ssh:// .... not git? :)

ssh hosts already set up... was just wondering how to get permission. :)

GavinFernandes commented on 2017-08-23 11:44

Ohh yeah I forgot, thanks for reminding me, you need to click the adopt package button on this page to the right, that should be all that's required.

As for your question about the honour system, the arch wiki is a better authority on it than me, but I know for a fact that in the aur, if you adopt a package, you can push to it freely, and you won't have your account killed. Once you adopt a package, you'll find two "Git Clone URL:"s on its aur page (this page), and you need to clone with the one beginning with "git:/". The one beginning with "git:/" allows you to git push (as long as you have your ssh keys set up). The one with https:/ is the one used by aur helpers and normal users and doesn't allow git pushes.

Btw if you have incorrectly set up or registered your ssh keys, then you won't be able to git clone.

Important: you might need to set up a ssh_hosts file to tell your computer which key to use for aur. If you need further help, comment here or email.

raster commented on 2017-08-23 11:22

ok - actually i just changed mine. using a custom key for aur... but how do you approve my ssh to be able to push? do you mean i can just push with no approval or other auth from you or anyone else once i have an ssh registered? it's an honor system of "only those who are trusted/permitted to push should do it, or they will have their accounts killed" ?