Re: Security and repository properties

On Oct 12, 2007, at 9:35 AM, Bicking, David (HHoldings, IT) wrote:

> Perhaps I missed it in the book, but I don't see any means to secure
> repository properties. The one two cases I see where this is
> important
> is the "needs lock" and "externals" properties. I can see where
> certain
> maverick developers might decide "this is only for the stupid
> programmers, not me" (yeah, I work in a corporate environment, and
> have
> known people like this). Is there a way to secure certain property
> types? If not, is there a chance it would be considered as an
> enhancement?

Only by the hook scripts. I don't think this would make it into svn
core itself and we would leave it to be implemented by a hook script.

I could see people deleting svn:needs-lock, but removing an
svn:externals would break a build, so why would people remove that one?

>
> I suspect the (perfectly reasonable) answer will be "use a pre-commit
> script". If so, do any of you happen to know a canned one I can lift?

I'm not aware of any implementations of such a hook script.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org