[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion Vision and Roadmap Proposal

From: Greg Stein <gstein_at_gmail.com>
Date: Sat, 10 Apr 2010 19:47:51 -0400

On Sat, Apr 10, 2010 at 18:04, Alexey Neyman <stilor_at_att.net> wrote:
>...
> I am not against standardizing most common approach. I just think it would be
> wasteful to focus on the issues that could be easily dealt with by configuring
> the repository.
>
> Here's an idea: have 'svnadmin create' populate the hooks that will perform
> enforcement of some of the desired models. E.g.:
>
> $ svnadmin create --model=none <PATH>
> [default] Creates an empty hooks area, allows for the flexible configuration
>
> $ svnadmin create --model=ttb <PATH>
> Creates /{trunk,tags,branches} directories in the repo, adds hook scripts that
> enforce tag immutability.
>
> $ svnadmin create --model=project_ttb <PATH
> Same as above, for the /{PROJECT1,PROJECT2}/{trunk,tags,branches} layout.
>
> These should provide good starting point for most projects, then the
> repository admin could fine-tune the settings as he likes it.

hahaha... it is very funny that you spec'd the above. I *implemented*
something almost exactly like the above, way WAY back in the first
year of svn development. It provided templates for both hooks and an
initial repository [layout] commit. We ripped it out soon thereafter
because it was just too easy for an external script to do this kind of
work, rather than building it into Subversion itself. :-P

IOW, yes I agree with the concept. I'm probably still in agreement
with the others who asked me to pull the feature: a simple script can
manage the above.

>...

Cheers,
-g
Received on 2010-04-11 01:48:17 CEST

This is an archived mail posted to the Subversion Dev mailing list.