Michiel Meeuwissen wrote: > Pierre van Rooden <[EMAIL PROTECTED]> wrote: > >>I think the problem with jars in CVS is that CVS tends to parse/alter >>code (i.e. replace $Id$ codes). There may be other problems too. CVS >>_seems_ mainly intended for text. > > > I agree, but my remark was only that IMHO _size_ is not an issue, so that as > far as i am concerned that argument better can be dropped.. >
True, size is one of the issues, but probably not the most important one. > >>Anyway I don't see much point in keeping a cvs of jars. > > > I do. It would be _very_ convenient. > But wouldn't store them somewhere on mmbase.org achieve the same? If they are stored in cvs, updating cvs will be very slow (when someone uses 'cvs update'). Ftp or even http will be much faster for binary stuff. Gerard
