Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 504592 - dev-python/python-efl: Python bindings for enlightenment foundation libraries
Summary: dev-python/python-efl: Python bindings for enlightenment foundation libraries
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal enhancement with 2 votes (vote)
Assignee: Default Assignee for New Packages
URL:
Whiteboard:
Keywords: EBUILD
Depends on:
Blocks:
 
Reported: 2014-03-14 14:18 UTC by Martin Schötterl
Modified: 2015-12-31 01:22 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
dev-python/python-efl-1.9.0.ebuild (python-efl-1.9.0.ebuild,2.33 KB, text/plain)
2014-03-14 14:18 UTC, Martin Schötterl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schötterl 2014-03-14 14:18:09 UTC
Created attachment 372654 [details]
dev-python/python-efl-1.9.0.ebuild

I tried to make a new ebuild for python bindings for joined Enlightenment Foundation Libraries. From what I've tested, the ebuild seems working fine on my system, but still it's my first one, so I'm not sure if there's everything right...

Especially I'm not really sure that everything I have in DEPEND is not runtime dependecy as well and furthermore the graphviz useflag is currently used only to pull in the media-gfx/graphviz, because I haven't been able to come up with a simple way of disabling graphs in case that graphviz is allready on the sytem - sugestions welcome!

-ebuild should be ready for use as a live ebuild as well, as soon as others enlightenment live ebuilds are working as well - haven't been able to test it yet
-I'm not using the enlightenment eclass for this one, because it unnecessarily depend on doxygen for documentation and it's not currently compatible with distutils-r1 eclass..

Thank you for your time and feedback!
Comment 1 Ian Delaney (RETIRED) gentoo-dev 2014-04-07 04:49:10 UTC
What's the intent here?  You want us to just add it to portage in the python herd?  You wish to proxy maintain it under guidance?
Comment 2 Dirkjan Ochtman (RETIRED) gentoo-dev 2014-04-07 07:07:21 UTC
Unless the EFL herd wants this, I don't think we should take it unless a python herd member is willing to spend time maintaining it, or more people turn up who think this would make a good addition to the tree.
Comment 3 Martin Schötterl 2014-04-09 20:59:11 UTC
To clarify my intentions..
I originaly wrote this one just because the python-efl package is needed by enlightenment's econnman module, which I wanted to test, and it comes to me as a good idea, that portage should do the work instead of me compiling things out of the tree..
Next thing was, that after joining the EFL libraries in mainstream last year, there are many ebuilds, that still don't follow it - so this I hope would be my little contribution to gentoo EFL team effort, if they take it...I'm even willing to proxy maintain this one - it is the rigt thing, if I'm not a gentoo developer? - if it helps, and no one from gentoo EFL team want to take it in the moment..
I gave it here mainly because it's my first ebuild and I thougth, here will more people see it and point to me any obvious mistake, that I've made..
So thank you all for your time and help!
Comment 4 jeremiah 2014-12-04 02:48:10 UTC
Newest version is now 1.12.0:
https://phab.enlightenment.org/phame/live/3/post/python_efl_1_12_0_release/

P.S. Should I put this as a separate version bump request or keep it here?
Comment 7 Bertrand Jacquin 2015-12-31 00:34:35 UTC
(In reply to SpanKY from comment #6)
> 1.16.0 version now in the tree:
> http://gitweb.gentoo.org/repo/gentoo.git/commit/
> ?id=dd1fff4735b3bc62f9fa362955824943992a9edb

Thanks for this ! Do you mind to add a stable ebuild for stable EFL ? That would be grand
Comment 8 SpanKY gentoo-dev 2015-12-31 01:22:02 UTC
(In reply to Bertrand Jacquin from comment #7)

stabilization will follow normal processes ... so at least 30 days