In article <[EMAIL PROTECTED]>, Ronald Oussoren <[EMAIL PROTECTED]> wrote:
> What I'd like to see is a collection of binary packages that are > created from a set of recipies (somewhat like what DarwinPorts does, > but without sucking in a second installation of unix). That way it > should be possible to (mostly) automaticly rebuild the binary > packages when new versions of software are released, and when a new > version of Python is released. I agree. I'd be nice to have a recipe for any packages on pythonmac.org that aren't trivial to build. (Ditto for eggs, I suppose; I've not yet tried to learn how to make eggs -- binary or otherwise. Any good basic tutorials around?) > In an ideal world we'd have the same set of software available for > python 2.4, python 2.5 and Apple's python installation. The only way > to get there is by using a toolset that does most of the work, > manually building software and checking that everything still works > is too much work. That sounds wonderful -- publish a script instead of a description of what to do. But even a recipe is much better than nothing. And to that effect...I am willing to serve recipes for building Mac versions of python-related software (I already serve a few). But we're talking basic here, no wiki, no database, each recipe is a page, with one table of contents page, you send me an update when you want to fix or improve something. -- Russell _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
