On Dec 21, 2006, at 10:48, Tim Bingham wrote:
> I'd like to put my hook scripts under revision control and have the
> copy on the svn server automatically checked out when a modified
> hook script is committed. (I'm coming from CVS where this is
> handled automatically by the "administrative files database" in
> CVSROOT, the files to checkout being listed in the "checkoutlist"
> file.)
>
> I'm looking for advice and suggestions. e.g. is there a tool, a
> contrib or example that does this? Is there a reason that
> Subversion doesn't provide this feature and that I'll trip over if
> I try to implement this myself?
>
> Committing the hooks scripts is, of course no problem. I can also
> see how the automatic checkouts can be triggered from 'post-
> commit'. Additionally, I expect to mimic CVS and create the
> equivalent of the "checkoutlist" file.
>
> I not sure of the best way to update the copies of the scripts on
> the svn server. For example can I simply make my "hooks" directory
> a working copy? Is that safe?
Sounds like you're on the right track. Yes, you should be able to
make the hooks directory (and config directory, if you want) a
working copy from a repository. When you make changes, you can commit
right from there. If people make changes elsewhere and you want them
automatically in place on the server, your post-commit hook can do an
"svn up" of the working copy(ies). I'm guessing the reason Subversion
doesn't directly provide this is that it's pretty easy to set up
yourself.
--
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
Received on Thu Dec 21 19:14:37 2006