On Sun, 10 Sep 2006, Chia-liang Kao wrote:
> GOAL
>
> To allow high-level applications create "projects" and
> "branches or tags within project", in the location by an agreed and
> configurable convention. This would also allow hook scripts, such as
> those preventing modification of /tags, to be written more portably.
>
> IMPLEMENTATION
>
> Property "svn:project:<projectname>" on '/', containing a spec like:
>
> [path]
> trunk = /path/to/trunk
> branches = /path/to/branches
> tags = /path/to/tags
> hooks = /path/to/hooks
>
> [address]
> admin = admin@host.org
> commit_url = svn+ssh://svn.host.org/project
> public_url = svn://svn.host.org/project
>
> There should be a list of standard names of commonly used meta-data,
> including at least those listed above. None of these meta-data should be
> mandatory.
>
> Where to put the property:
>
> * Versioned property on '/',
> - Pros: Versioned.
> - Cons: Requiring read access on '/' to make use of the meta data.
Requires a checkout of '/'. Afaik propset and propedit do not accept
URL's. So this seems to not be an option.
> * Unversioned property on r0
> - Pros: Works out-of-box with repository that has acl.
> - Cons: Unversioned.
* Files in '/svn_repos_config/' ?
- Pros: Versioned, easy to copy or merge, integrates with authz.
- Cons: Needs a toplevel directory in the repos.
> Personally I'd prefer the r0 one, as versioning such properly is
> actually not so interesting, while having the properties more
> accessible would make it easier to build applications on it.
Have you also thought about repos reorganisation? At the moment I don't
see anything that could break, it should be possible to find old deleted
branches/tags by looking up the log of the branches/tags dirs.
Just my 2 cents.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 12 01:18:32 2006