2009/8/27 Jeremiah Foster <jerem...@jeremiahfoster.com>: > > On Aug 26, 2009, at 19:52, Ed Bartosh wrote: > >> 2009/8/26 Jeremiah Foster <jerem...@jeremiahfoster.com>: >>> >>> On Aug 26, 2009, at 18:05, Andrew Flegg wrote: >>> >>>> On Wed, Aug 26, 2009 at 16:25, Ed Bartosh<bart...@gmail.com> wrote: >>>>> >>>>> 2009/8/26 Andrew Flegg <and...@bleb.org>: >>>>>> >>>>>> On Wed, Aug 26, 2009 at 16:17, Ed Bartosh<bart...@gmail.com> wrote: >>> >>> This is a good point - we have a chance to reduce the bloat of the >>> debian system that is designed for at least eight official >>> architectures when we build only two. Plus there might be a way to >>> innovate and to simplify the entire build process over time which >>> would be a huge win for developers. >>> >> I understand that. If you may notice we're already using our own >> builder instead of wanna-build or whatever Debian uses for this. > > Some of the upstream build stuff is quite good though. And is python really > the right tool to do builds? As far as I am concerned it has some drawbacks > in this particular area: > > 1. The GIL problems make it unsuitable for multicore machines > 2. Python is slow in general > 3. The vast majority of existing build systems are written in > something else, so there is a bit of wheel re-invention with python > This is a bit out of scope of this thread. If you're really interested in comparing Python capabilities with other programming languages in this area feel free to create new thread for that.
Regarding slowness of the Maemo build system in my opinion it isn't a result of using Python, but lack of resources (only one build host) and brain-damaged repository management system. And if it's not changed in near future I doubt that change to another build system will help. -- BR, Ed _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
