Re: Centipede & multiple projects
Glen Stampoultzis <[email protected]>
| Newsgroups | gmane.comp.krysalis.user |
|---|---|
| Message-ID | <[email protected]> |
At 02:14 AM 15/04/2003, you wrote: >The problem with the current multi-project-in-module approach is that it >uses only one centibuild file, which *starts* the process. Hence even if >we make the multiproject system get the right buildfile, we still need to >tell centipede which buildfile to start with, and which project. Bleah. :-P > >So real multiproject builds should be done with Gump, that's all. What we >have now is a short-circuit that works for one centibuild file and in the >same module. > >It's becoming IMHO more evident that the best thing, as we said some days >ago, is to zap it and use an external system to drive multiproject builds. > >If we want we can still do it with the code we have, with a new cent >script that calls that code, but the best thing is to use Gump and that's all. > >No? How does this fit in with Sam's recent random thought on converting gump to python? Do we want python as a requirement for our users? Regards, Glen