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

Re: New Server Installation, Access File, and Auto-Props

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-12-05 06:34:42 CET

On Dec 1, 2005, at 23:17, Res Pons wrote:

> 2. I got my access file in conf/ working restricting access and
> rights. Is it possible to block access per file rather per
> directory? There're couple of files in a directory which contians
> many subdirectories that only few authorized users should modify
> but all other users should have r/w access to the subdirectories
> beneath.

I don't know whether that is possible, sorry.

> 3. I'm trying to turn on and enable the auto-props but I don't
> see /etc/subversion being created. Do I manually create this
> directory? Who should be the owner? Root or www? I copied
> "config, servers, and readme.txt" from Windows side to this newly
> created subdir and tweaked the config file and set enable-auto-
> prop=yes and created [auto-close] with file pattern entries
> underneath it like so *.txt=keyword=Id. Created a new text file,
> checked it in successfully but when I executed "svn proplist
> filename..." I did not see the new properties. Could someone
> please elaborate on this further. Does Subversion automatically
> and magically by default look for /etc/subversion and executes the
> files? I'm lost and this part is not working for me.

auto-props are a client-side thing, not a server-side thing. The
clients need to set up their config files with the auto-props they
want. Any config file in /etc/subversion is merely used as the
default for clients running on that same computer who don't have a
custom config file in their own Subversion directories. So unless
your users are logging in to the Subversion repository server with
SSH (which you said they're not) then an /etc/subversion directory on
the repository server won't do anything for anyone.

What you should do is create a standard config file and distribute it
to your users. Then you should install a pre-commit hook on the
server which verifies committed files against that master config
file, and rejects commits that do not comply. I recently posted a
link to a Python script that someone had written for this purpose.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 5 06:36:39 2005

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