Re: user defined property names

John Norris wrote:

>> Please no. I really don't like to have a setting to point to another
> setting.
>> Either store this in the registry, or in a config file. If you use a
>> config file, store that file in %APPDATA% like Subversion and any other
>> good program does.
>
> But then there are dozens of copy of the config file so that is not good.
> Anyway as I said later there is a better way.

As it is with every other config file out there.
You have to clearly separate config files from domain settings. We're
talking about config files here, which are 'local'. Server side settings
are something different.

>>> I took this a stage further and stored the property names in two
> properties
>>> (once gain, one for files, one for directories).
>>> This approach has a number of advantages. There is no need for a separate
>>> admin dialog from the original approach. There is no need to read files
> and
>>> convert from ASCII to Unicode. Admin may be easier as there is nothing to
>>> set up on the PC.
>>> The disadvantage is where the properties should be attached. So that the
>>> whole directory structure (trunk, branches, tags) is covered when the
>>> properties are applied, the whole repository has to be checked out rather
>>> than just trunk. Also, its possibly not as obvious. Security should be OK
> as
>>> the directory the properties are attached to can be made read only.
>>> So, I am not sure where the properties get attached but other than that,
>>> "the user defined property names defined in a property" approach is the
>>> preferred option.
>>> Comments?
>
>
>> You could create a new "project property" (like e.g. tsvn:logminsize).
>> That property then could have a list of other predefined properties.
>
> Which is what I descibe above. Except that I have two properties, one for
> files and one for directories. But to go back to my original question. With
> this approach, where do the properties get attached in the directory
> hierachy? For testing I have put them on trunk but they would be better
> placed on the "vob-tag" except that would mean bring down the whole
> repository structure. But its only the once to define the properties and
> then its back to normal.

Search the mailing list for "project properties", how they're
implemented in TSVN and what the problem is with those. They're also
described in our docs.

What you (and many other people here) want is server side
configurations. But Subversion doesn't have such a feature, that's why
we introduced the project properties. Of course, that's just a
workaround for the missing server side configs and have their own
problems (as you have noticed: where to apply those).

There's an open issue in the Subversion issue tracker about server side
settings. But nobody's working on it (yet).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org