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

Re: Repository-defined autoprops.

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-05-27 23:17:52 CEST

kfogel@collab.net wrote:
> SteveKing <steveking@gmx.ch> writes:
>
>>Another idea comes to mind. Instead of using inherited properties, why
>>not use a specially named config file stored in the repository?
>>If per-directory isn't needed, a somewhat simpler solution could be:
>>
>>- if a file named e.g. .repoconfig is in stored in the repository
>>root, then use this as the repository config file (same format as the
>>config file now has).
>>- After every update/checkout/... (operations that update the working
>>copy) also fetch the config file
>>- the config file is stored in a subfolder in the Subversion config
>>folder (%APPDATA%\Subversion\repoconfigs\{repo-uuid} on windows for
>>example).
>
>
> This was exactly the proposal I wrote and then erased :-), yeah.

I've also documented this in issue 1974
http://subversion.tigris.org/issues/show_bug.cgi?id=1974

Just curious: why did you erase the proposal?

>>Advantage:
>>- easyer to implement (I think)
>>- same format as the normal config file, so user already know how it works
>>- only one copy of the configuration stored, not on each and every
>>file/folder in the working copy as with inherited properties
>>
>>Disadvantage:
>>- only per-repository, not per-folder (even though the config file
>>could have sections for subfolders)
>
>
> No need to have sections, it can just use paths.
>
> However, one problem is that now everyone needs write access to a
> global file. What if the projects do not trust each other, but still
> share a repository?

No need to give everyone write access to that file. Only project admins
would really need write access. And if the project admins don't trust
each other, the repo admin would have to do the job. Basically the same
as with hook scripts - users don't usually have access to those either.

>>- to edit that file, one has to check out the repository root
>>(non-recursively), edit the file and commit it
>
> Better to have it in a subdirectory of the root. Greg Stein has a
> great solution for this:
>
> You put it in a subfolder named "/config". But, that's configurable,
> via an svn:config-dir property set on the root directory of the
> repository! So if people need to use "/config" for something else,
> they can just set that property. Subversion would always look where
> the property points; if no property, then default is "/config".

That's even better!

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 27 23:18:37 2005

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