Re: Repository-defined autoprops.

On 2005-05-27 15:29-0500, kfogel@collab.net wrote:
>
> 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?

One option is that we have a that special directory (defined by
property), and under it we have subdirectories, one per project. This
way different projects under same repository can protect their own
config file. Logic to look for the spesific config file could be:

for path /project_1/trunk/foo.c:
   if /config/project_1:
      # This is editable by project_1
      use /config/project_1/global.cfg

   elif /config/global.cfg:
      # this is set up by repository admin
      use /config/global.cfg

   else:
      use default

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org