> Yes, that was the idea. > > It could even be done (I think) with the CVSROOT/modules configuration (so > excluding 'mmbase/scripts' from the 'mmbase' module and including it in a > new one), in that way the cvs history stays accurate. > > Another option would be to simply put only 'build.xml' in the root, because > that is the most interesting script anyway.
Putting scripts in a other module is a good idea. > Yesterday on IRC also the idea of putting the stuff in CVS which is now > auto-downloaded in the build.xml came up (again) (say a module 'lib') > > This has some obvious advantages: > > 1. The build.xml can be considerably simplified > 2. It is garanteed that every version of MMBase can be recompiled easily, > because there is no chance that the external resources get disfunctional. > > The main disadvantage is I suppose that it doesn't 'feel right' to check > external products in CVS. and that all kind of stuff should also be checked > in because they must be distributed together or something like that. I consider this a bad idea, CVS isn't equipped well enough to handle binary files, especially large ones. This will mean our repository will grow large very quickly (especially with new version of things). There might also be licensing issues with some of the binaries. -- Rico Jansen ([EMAIL PROTECTED]) "You call it untidy, I call it LRU ordered" -- Daniel Barlow
