cvs-like functionality re modules and admin files

Hello,

We have a large (9GB, 7 years of code) cvs repository, which I'm
evangelizing that we move to subversion. A couple of questions about
admin files:

1) cvs versions the administrative files b/c CVSROOT is a special
directory, whereas subversion does not. It would be nice if admin
files (e.g. hooks and files they use) were under revision control. Is
there a recommended practice in this regard?

2) We have a long history of using cvs modules, so that various
projects can select the directories of interest on checkout. Right
now, we plan to write a script to parse the existing modules file and
do checkouts based on those modules. I looked in collab.net's contrib
for such a script. Has anyone written something like this and/or is
there a recommended practice?

Thanks,
Kylo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 3 18:54:05 2007