>    1. As long as we'll have to run a script anyway, a script which generates
>    the CVS directories on the fly would probably be about as easy as one to
>    convert the current ones, and could also be useful for those who still
>    have earlier source trees lying around.

> this is false.

> the script to change things will probablyu just add something like
> "anoncvs.netbsd.org:" to the start of the CVS/Root files.  nothing
> else will need to change.  to *generate* the CVS dirs, you need to
> know lots of things, including the RCS version of *every* file in
> the source tree.  the scales of these two projects are massively
> different.

Oops... I was looking at the directory entries only (which would be simple
to generate) and missed the file entries, which would require a lot more
work... comment withdrawn.

And for those of us who use our own cvs tree to track the sources, I'm
currently working on modifications to cvs to allow it to sanely handle
branches in a vendor source being tracked via import (e.g. allowing imports
and local modifications on both branches...)

jdarrow

--
John Darrow
Computing Services, Wheaton College, Wheaton, IL
John.P.Darrow@wheaton.edu