On Friday 13 November 2009 06:44:37 am Tarek Ziadé wrote: > Here's my proposal for this to happen, if you (and others) want to > contribute: > > Let's build this new "configure" command in Distribute 0.7, together > with the APIs to read/write the data. > > Then let's change the other commands consequently (without thinking > about backward compat first) > so we can try out this new behaviour.
Fourthought's 4Suite distutils extensions already provide this behavior. You may consider looking at how the 'config' command is handled there as a guide in implementing this. Or just copy it wholesale, for that matter, as it is my doing. > Once it's proven to work good, we could publish Distribute 0.7 with > it, and depending on the community > feedback, we could integrate it to Distutils and work on the backward > compat part. > > this two phase step wouldn't be a problem imho, for early adopters > that would use and test it. The exact thing being described has been done in 4Suite for 6 years (along with many other distutils improvements). Feel free to take or discuss or request help with any of the features/additions (like FHS layout of files) in the 4Suite distutils extensions. The code is available for browsing: http://cvs.4suite.org/viewcvs/4Suite/Ft/Lib/DistExt/ The way we've impl'd 'config' was as a prerequisite for 'build', just as 'build' is for 'install'. If any of the options stored by the 'config' command are overridden via 'build' or 'install' options, the 'config' command would be re-run to store the "new" choices. Any questions or just simple help with integrating a similar system, just let me know. Been there, done that. Jeremy -- Jeremy Kloth http://4suite.org/ _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
