Scott Sanders wrote: > > I do feel that the <cvs/> element belongs in the <module/> element, but > I *hate* the fact that the project is not explicitly saying that it > depends on it. Not all projects defined in a module depend on the > <cvs/> being executed. This is want I want to fix eventually.
How much more explicit then ENCLOSURE can you be? ;-) Here's a simple rule: "projects depend on the cvs sources from the modules which contain them." Makes sense to me. If vindico were to internally generate virtual project definitions from module definitions which contain <cvs> elements by taking the name of the module and appending "-cvs", and adding the dependencies which are implied by the above rule, then we could stay with the current project definitions. Make sense? - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
