On Saturday 14 November 2009 05:14:05 pm Tarek Ziadé wrote: > On Fri, Nov 13, 2009 at 3:46 PM, Jeremy Kloth <jeremy.kl...@gmail.com> > > 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. > > So did you end up changing the way options are passed to the commands, > or do you just have a specific "config" command that looks over other > options passed to the other commands ?
It is done with the 'config' command having all the options used by the other commands. The other commands would then look up their options' values from 'config' (if not supplied on the command-line). If, for example, `--prefix` was supplied to 'install', the 'install' command would then cause the 'config' to redo its stored options. If at all possible, I would eliminate the redundant options on build_*/install_* and leave them solely on 'config' as it greatly simplifies the interaction of the commands. Jeremy -- Jeremy Kloth http://4suite.org/ _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
