Re: filtering import and setting lock

Tremal,

Please keep replies on the list so others can benefit from the
discussion.

On Oct 23, 2006, at 10:50, Tremal Naik wrote:

> 2006/10/23, Ryan Schmidt:
>
>> I think you'll want to modify ~/.subversion/config on the client,
>
> ok, but what are the server config file for?

I am not familiar with /etc/subversion/config; no such file exists on
my system.

> Suppose I want to grant access to many users, how can I manage that
> everybody has the correct ~/.subversion/config settings? And suppose
> that my users are windows users? How can i set the options for them?
> Supposing that they can use whatever client they wish (I'ma a very
> democratic subversion administrator)?
>
> I'm not asking this to polemize, but I think there should be a
> mechanism to centralize this kind of settings. Maybe with the use of
> hooks?

There is no server-side way to cause auto-props or global-ignores to
occur. They must be set on the client.

Then, you can install a pre-commit hook on the server side that
rejects any commit that does not conform to your requirements. For
example, if a .java file is being checked in and it does not have the
svn:eol-style property, reject the commit and inform the user to set
the property and try again, or set up the auto-props. You can even
show a URL where the user can get a pre-configured config file they
can just drop into their .subversion directory.

I believe on Windows, the config file is in C:\Documents and Settings
\<username>\Application Data\Subversion

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 23 19:34:49 2006