Gerard van Enk <[EMAIL PROTECTED]> wrote: > >>It *can* be done, but for every new jar, cvs creates a whole new file > >>on the cvs-server, instead of just storing the latest version and the > >>differences. So if the jars are big, alot of storage is needed. > > > > > >Putting the jars on www.mmbase.org will use the same amount of space. > >Both cvs and http are on the same machine. So, what's the difference? > > If you put them on www.mmbase.org for download, you can replace the old > one with a new one, in cvs the newer one will be stored next to the old one.
Then you still can't rebuild older versions. Btw. the libs are stored _every day_ now on mmbase.org (by the nighly build). So the occasional update in CVS will have only a minor effect compared to this. I think I heard better arguments agains putting the external libs in CVS then the amount of disk-space on the server which it would cost. Lets say that someone updates a library once a month, and that a it would cost then 5 Mb in the CVS repository. 5 Mb/month is nothing. I don't think it should be a valid point in this discussion. Michiel -- mihxil' Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 []()
