On Thu, 14 Mar 2013 20:49:46 +0100 Davide Andreoli <d...@gurumeditation.it> wrote:
> 2013/3/14 Kai Huuhko <kai.huu...@gmail.com> > > > 14.03.2013 05:02, Doug Newgard kirjoitti: > > > ---------------------------------------- > > >> Date: Thu, 14 Mar 2013 10:52:12 +0900 > > >> From: cedric.b...@free.fr > > >> To: enlightenment-devel@lists.sourceforge.net > > >> Subject: Re: [E-devel] [econnman] [patch] update for new bindings > > >> > > >> On Thu, Mar 14, 2013 at 9:10 AM, Doug Newgard > > >> <scimmi...@outlook.com> > > wrote: > > >>> I recently became aware that there was a release of econnman a > > >>> while > > back (http://packages.profusion.mobi/econnman/econnman-1.tar.gz), so > > there's not really a need to keep the version in SVN compatible > > with the release versions of EFL and the old python bindings. The > > attached bindings-update.patch adapts econnman for the new bindings > > from DaveMDS and kuuko. configure.patch removes the pkg-config > > checks from configure.acbecause the new bindings don't provide pc > > files. > > >> This lack of .pc disturb me. Is that expected or is that due to > > >> the ongoing merge ? > > > I don't know, but it makes it easier to build it for multiple > > > versions > > of python. If you want both 2 and 3, for example, it's nice to not > > have conflicting files out of the box. Since you don't really have > > any use for include or lib flags, the only thing it would be useful > > for is checking if something is installed. > > > > > Patch looks good to me. k-s has the final word regarding econnman. > > > > Since we switched to using distutils we no longer provide a pc > > file. One pythonic way of checking if a package is installed is to > > test import it in your install script: > > > > #!/usr/bin/python > > try: > > import efl > > except ImportError: > > print("Thou needs moar enlightenment in thy snakepit!") > > sys.exit() > > > > > indeed, this is the 'normal' way of checking availability in python, > and there is no reason to check for libs when doing make, they > are not necessary to "compile". > > ...also I think we should use setup.py instead of autofoo, it's > the python way of doing it and handle better py2/3 installation. > > as kuuko says k-s has the final word on this For those of us that are not snake handlers, what's the proper generic way to build the various python projects we have in git/svn? I'm trying to keep my new build script generic, but it's not working on the python stuff yet. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
