[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 21:07:29 CET

On Dec 5, 2005, at 11:44, Res Pons wrote:

> On Dec 4, 2005, at 23:34, Ryan Schmidt wrote:
>> 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.
> We only use the one server with 1 repo and multiple projects under
> it; no multiple repos. So then, could I ask all users to delete
> their winxp local config files and just let the one in /etc/
> subversion to be the default, would that work?

Again, if all these users are logging in to the Subversion server via
SSH and using the svn command line client while logged in to that
server, then the config file in the server's /etc/subversion
directory will have effect. If your users are using clients on their
local Windows machines, then it will not.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 5 21:10:50 2005

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