On 7/3/06, Mattias Engdegård <mattias@virtutech.se> wrote:
> Steinar Bang <sb@dod.no> writes:
>
> >Another problem is that subversion UIs, such as eg. subclipse, have to
> >guess at the directory structure chosen for the tags if _they_ would
> >like to offer a friendlier interface to tags and branches
>
> To expand on this: While subversion elegantly allows tags and branches
> to be organised hierarchically, there is no way a tool can infer this
> from the layout (consider "/frobulator/tags/releases/7.2" where the
> tag is "releases/7.2").
>
> Local conventions is the only recourse here, like adding magic
> properties to directories in tags/ and branches/, but this reduces the
> commonality that makes standard tools useful - no good if everyone
> have to write their own log browser, IDE plug-in, etc.
So if I read all this (and the previous thread) correctly there seems
to be interest in collecting a best practices standard for holding
configuration information relevant to:
1. repository layout (and perhaps other svn properties not yet
metioned/thought of)
2. layers used on top of svn (wrappers, IDEs, et alia?)
This would be completely optional and not even a part of svn core
code, but rather a documented, extensible, standard/recommendation
that contrib tools and "third party" apps could gradually start to
support.
Does that sound somewhat correct?
I'm imagining some sort of document (wiki?) that recommends various
filenames and formats for svn config things under some well-known
repository url (e.g., 'BASE_REPO_URL/_config/svn/...'), and other
projects can spec their own formats under an equally
well-known/guessable, yet entirely related, repository url (e.g.,
'BASE_REPO_URL/_config/{"subclipse",other_project,company_name,"site"}/...'
).
But maybe I've wandered off into left field on my own...
-Erik
Received on Fri Jul 7 02:51:03 2006