Re: Subversion hooks directory as a Symbolic link.

>>>>> "Lakshman" == Lakshman Srilakshmanan <lakshman.srilakshmanan@tradingpost.com.au> writes:

 Lakshman> Hi All, I am looking for feedback on your thought in doing
 Lakshman> the following.

 Lakshman> 1. Move hooks directory in the repository to outside the
 Lakshman> repository eg. mv /repos/Enterprise/Common/hooks
 Lakshman> /repos/hooks 2. put a symbolic link in the
 Lakshman> /repos/Enterprise/Common eg. ln -s /repos/hooks
 Lakshman> /repos/Enterprise/Common

 Lakshman> The reason I want to do this is because I will have
 Lakshman> multiple repositories and need to maintain the same hooks
 Lakshman> scripts across all repositories.

That works fine. I've done that with my hooks and also with the
access control files in repos/conf. In fact, both are softlinks to a
working directory holding a checkout of an "administrative data"
repository, and that working directory is updated on every commit. So
I can administer Subversion from anywhere, and any changes
automatically take effect. The result is a bit like the auto-publish
behavior of CVSROOT in CVS, but more general.

         paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 17 19:17:42 2006