Rob van Maris <[EMAIL PROTECTED]> wrote: > > ----- Original Message ----- > From: "Eduard Witteveen" <[EMAIL PROTECTED]> > > > If i understand Michiel correctly he wants to move > > /src/org/mmbase/scripts > > to > > /scripts > > > > This is exactly the same as what you are proposing.. ?? > > Is it? My point is I'm in favour of a single module with a fixed file > structure, as opposed to a number of independent modules. > That's not going to stop anyone from checking out subdirectories (like > all/src/org/mmbase or all/scripts), but at least the overall directory > structure is fixed for the standard build.
I agree. Therefore I created the 'all' module, which will of course also contain 'scripts'. The existing modules 'mmbase' 'config' 'html' 'documentattion' will stay to exist, but there is no need to use them. 'scripts' will be an alias for cvs co -d script mmbase/scripts or something like that. This fact can be totally be ignored, in my view this is an 'implementation issue' for a situation completely the same as what you said: that one cvs checkout can produce the directory tree which one needs to compile and package mmbase. cvs co -d mmbase all will do this, and I think this is the command that then should be communicated to new users/developers. In my opinion it doesn't matter that there are shortcuts to get other things like 'cvs co src', 'cvs co config', 'cvs co script' etc. Michiel -- Michiel Meeuwissen Mediapark, C 107 tel. +31 (0)35 6772979
