[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 22:55:14 CEST

kfogel@collab.net wrote:
> This mail is about propagating repository-defined autoprops to
> clients, a feature we don't have, but wish we did.
[snip]
> So there you have it. We want:
>
> * Disconnected operation with a working copy.
>
> * Connected operation without a working copy.
>
> * Per-directory instead of just per-repository (maybe -- I at least
> am not sure about this).
>
> * It's an open question whether mapping directoryglobs<->props is
> important. Right now my guess is it's not.
>
> This might be a tall order.
>
> Frankly, the only good solutions that come to mind involve inherited
> properties. I don't, however, have a good specification for how
> inherited properties should behave, nor how to implement them.

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).

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)
- to edit that file, one has to check out the repository root
(non-recursively), edit the file and commit it
- if a project already has such a file in the repository root stored,
this change would break. Although I don't think that any project out
there really has such a file stored there. If in doubt, the file could
be named with a UUID.

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 22:55:53 2005

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