--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> Noel Yap <yap_noel@yahoo.com> writes:
> > Comments? Ideas? Preferences?
>
> Yes -- a preference to not do this :-).
That's two so far :-) I'll probably just wrap the
Subversion client then to mark the elements with
metadata indicating their types.
> I'm still not clear on the problem you're trying to
> solve. What's not
> working about the current model? What was the
> problem you encountered
> (and I do mean "encountered", not "anticipated")?
I'm encountering the problem trying to create a hook
that'll treat branches differently from tags.
Actually, I keep confusing myself (as may have been
evident ;-). Yeah, now that I'm rethinking this some
more, what I really want to do is differentiate
between directories and tags. For example:
/project # directory
/main # directory
/HEAD # directory
/0 # tag
/LABEL # tag
/branch # directory
/HEAD # branch
/0 # tag
/branch is really a directory and /LABEL is a tag
(which, to Subversion, is really a directory, too). I
want my hooks to create HEAD (which would either be a
directory or a branch) and 0 for directories (with
certain exceptions) and do nothing for tags.
> From what I've read, it looks like you could
> accomplish what you need
> with custom hooks, with no need to change the
> Subversion client. But
> perhaps I'm misunderstanding your problem. If you
> want people not to
> commit to tags, just protect the tag areas from all
> changes except
> adds.
One of the things I do want to do is protect the tags.
With the layout I'd like, the hooks would have to be
able to differentiate among directories, branches, and
tags.
> > Isn't it also a feature not to impose any
> particular
> > directory structure? If someone had wanted to
> treat
> > branches differently from tags (eg for
> permissioning),
> > currently, since Subversion can't tell the
> difference,
> > the only recourse is to have some convention
> within
> > the repository. The typical proposal is to
> separate
> > the namespace of branches from that of tags. Not
> > imposing separate namespaces would make Subversion
> > more flexible.
>
> Noel, it sounds like you're trying to duplicate an
> experience you had
> with another version control system. We're never
> going to be able to
> satisfy that. Just try it the Subversion Way, see
> how you like
> it :-)...
I'm stubborn :-). I really think it's not a stretch
for Subversion to support the above hierarchy. Since
noone is on my side on this and, in fact, some are
against the idea, I'll just wrap Subversion to supply
the info the hooks need.
I'd just like to further understand why everyone is
against the following:
1. Adding "svn branch" and "svn label" (which, BTW, I
seem to recall reading about in the doc).
2. Adding "svn:type" to indicate element types.
Thanks,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 15 17:59:20 2002