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

Re: [RFC] Server Dictated Configuration

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 05 Jan 2012 21:23:17 +0100

On 05.01.2012 21:03, Mark Phippard wrote:
> On Thu, Jan 5, 2012 at 2:42 PM, Ivan Zhakov<ivan_at_visualsvn.com> wrote:
>> On Wed, Jan 4, 2012 at 02:58, Paul Burba<ptburba_at_gmail.com> wrote:
>>> Mike Pilato and I have been kicking around some ideas on server
>>> dictated configuration recently and have put our thoughts into a wiki
>>> (full disclosure: this wiki was initially based on Hyrum's thoughts on
>>> the subject in https://svn.apache.org/repos/asf/subversion/trunk/notes/repos-dictated-config)
>>> :
>>>
>>> http://wiki.apache.org/subversion/ServerDictatedConfiguration
>>>
>>> We're at a point where it's time to solicit some wider feedback, so
>>> please have a look at the wiki and follow-up here with any concerns,
>>> thoughts, suggestions, etc..
>>>
>> I think most of use-cases can be solved by existing mechanism without
>> inventing something new:
>> 1. auto-props
>> TortoiseSVN already has 'tsvn:auto-props' property [1]. Which used to
>> automatically set properties for added files. It would be nice if
>> Subversion core support this property.
>>
>> 2. ignores
>> We can add svn:global-ignores property to define global (recursive) ignore mask.
>
> The approach TortoiseSVN and some other clients take does work pretty
> nicely but I also think they reveal the short comings in using
> properties. For convenience, TortoiseSVN does not force you to set
> these properties on every folder and instead will walk to the root of
> your WC to find them, but then this also exposes the problem that if
> you did not checkout the folder that has those properties you are back
> to square one. That is why I believe it makes sense for SVN to
> support it natively using an approach something like described in the
> wiki. Or at least weigh that approach versus using properties within
> the repository. Perhaps properties are the way to add the deferred
> feature of supporting overrides based on path?

overrides based on path - do you mean that properties would be
inherited, i.e., child items inherit the properties of the parent item(s)?
If that could be implemented, it would automatically solve the problem
of different configs for different paths.
And the best advantage of all:
users could set/modify the properties with their clients. No need to
contact the administrator and have him do it - believe me, Admins will
very soon get annoyed if such changes/modifications happen often.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
Received on 2012-01-05 21:23:56 CET

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