On Tuesday 10. February 2015, Russell Keith-Magee wrote: > > FTR - the "download and patch" approach is also the approach taken by Kivy > (and by extension, Python-Android-support).
Yes, it's often easier to do that than to get patches accepted upstream, though maintaining the patches can be a burden. [...] > The standard autoconf tools have really good support for building a single > source tree for a single platform; building multiple versions and merging > the results isn't an area where it is as capable. So - a 'helper' script > like this is an almost inevitable part of the whole process. What I'm not > clear on is: > > 1) Whether this helper script needs to be part of the "official" > distribution > 2) If it does, where is the right place to put the helper script. I'm not sure it should be "official" but I'm not the person you have to convince. ;-) > However, getting the patches for the existing build tools is still the > first step. On that subject, I looked at your Python-Android-support patches today with the idea that I might take the best bits from those, openembedded-core and python3-android. The patches are for Python 2.7. Would you recommend that I look at Kivy's patches instead or are you likely to update your repository? David _______________________________________________ Mobile-sig mailing list [email protected] https://mail.python.org/mailman/listinfo/mobile-sig
