IIUC, you have a stack of patches and a build invocation that works. A buildbot, travisci, and/or other Makefile build config with filename-tagged artifacts (such as cross compiled archives) would be easy to maintain.
Mercurial MQ or a bookmark would make rebasing for new CPython mainline releases easy. ( http://hgbook.red-bean.com/read/managing-change-with-mercurial-queues.html#sec:mq:start ) ... http://en.wikipedia.org/wiki/Continuous_integration#Best_practices On Feb 19, 2015 6:26 PM, "Cyd Haselton" <[email protected]> wrote: > Thanks to the help and input of people from this and the python-dev list > I've hacked together a nearly complete port of Python 3.4.2 to > Android...specifically the KBOX system running on Android. I'm currently > working at what I hope is the last bug...typing 'modules string' segfaults > the python binary. > > I started this with the mindset that the port was just a step on the way > to porting Mozilla's SpiderMonkey. I still intend to do this but I'm also > wondering if, given the huge amount of work it's been, there is any public > usefulness to this port. > > If so, what would be the next steps? Keep in mind that I am relatively new > to pretty much everything related to the Linux platform, code > development/contribution/maintenance and the like. > > Regards, > Cyd > > > -- > Sent from Android > _______________________________________________ > Mobile-sig mailing list > [email protected] > https://mail.python.org/mailman/listinfo/mobile-sig > >
_______________________________________________ Mobile-sig mailing list [email protected] https://mail.python.org/mailman/listinfo/mobile-sig
