Re: cvs-like functionality re modules and admin files

On Feb 2, 2007, at 18:34, Kylo Ginsberg wrote:

> 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?

You can check your hooks and configs into the repository if you want.
You can write a post-commit hook that would auto-update the configs
and hooks. This way, anyone could check out the hooks or configs on
their desktop, change something, commit it, and the server would auto-
update. If this is what you want, then it can be done.

> 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?

I believe you want svn:externals here. See the book:

http://svnbook.red-bean.com/en/1.2/svn.advanced.externals.html

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org