On Fri, 4 Mar 2005 19:25:06 +0100, Matthias Waechter
<Matthias.Waechter@tttech.com> wrote:
>
[...]
> > Through the use of the pre-commit hook, you can make the /tags
> > directory for a project be write-once (you can create a new tag, but you
>
> > cannot rename a tag, nor change any files within that tag).
> > I'm actually suprised that there isn't an example to do something this
> > included with the source. I'm sure someone else has written something,
> > but if no one speaks up, I'll do it myself, and it'll be in Perl, just
> > to annoy the Python zealots... ;-)
>
> Well, I am surprised to see so much information describing the behavior of
> a database is stored in unversioned, text-based files (hook-scripts,
> config files, access control). I think this topic requires a rewrite some
> day anyway ...
Well, that depends. I actually store the pre-commit hook in the repository
itself. I use a softlink in the hooks directory to point to the local location
where the pre-commit hook is stored. I then have a post-commit hook that
causes the admin areas of the server to be "svn up"ed if those areas
were touched in the commit. This includes the access control files
and the hooks and all of the administrative CGIs and repository browsing
tools (all of this is part of the insurrection project) This is in
live operation
right now in multiple organizations.
--
Michael Sinz Technology and Engineering Director/Consultant
"Starting Startups" mailto:Michael.Sinz@sinz.org
My place on the web http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 6 05:01:55 2005