Dominic Anello <danello@danky.com> writes:
> > I'm not planning to alter a commit transaction. I'm modifying a
> > property (which isn't version controlled anyway) *after* a commit
> > transaction. I understand why you can't modify a commit in a
> > pre-commit hook, but I don't see any issues in updating the repository
> > in a post-commit hook.
> ----8<----
>
> Properties *are* version-controlled. Revision properties aren't, but
> svn:mime-type isn't a rev prop. Furthermore, if you look at the help
> for svn propset, you'll see that ps without the --revprop flag only
> accepts PATHs as an argument, so you have to check out a working copy.
> Not to say it can't be done, but your hook script will both create
> additional revisions and need to manage working copies.
You are right about the different kinds of properties.
However, it is technically possible (though we strongly recommend
against it!) to modify versioned-controlled properties in the
repository without using a working copy. Just use the svn_repos_* and
svn_fs_* APIs, either directly or through some language bindings.
Again, don't do this in a pre- or post-commit hook. It's important
that repository txns remain exactly as clients committed them,
otherwise the client's working copy will be out-of-date but the client
won't know it.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 19:27:22 2005