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

RE: Server-driven configuration control?

From: Larry Walker <larryw_at_voicebox.com>
Date: 2006-03-15 02:39:57 CET

Until this happens, here is a workaround - put a client on the server
with appropriate tie-ins to the pre or post commit hooks. We are using
this approach to add need-locks and eol-style properties to added files.
The only downside is we send the user an email informing them that they
need to update their newly added files (and we provide them a list).

-----Original Message-----
From: Matt England [mailto:mengland@mengland.net]
Sent: Tuesday, March 14, 2006 5:14 PM
To: SVN Users email list
Cc: mengland@mengland.net
Subject: Server-driven configuration control?

I would like to see the Subversion system one day support server-side
configuration management of repo-wide activities. ie, I don't want to
have
to force, manual, client-side changes (as per things like the
"Standardize
on ASCII type: dos2unix pre-commit hook?" thread started here:
<http://svn.haxx.se/users/archive-2006-03/0516.shtml>, some text of
which
is commented below) in order to enforce repo-wide policies like standard

ASCII formats, etc.

Is this is Subversions future, however far out it may be?

-Matt

At 3/14/2006 04:55 AM, Ryan Schmidt wrote:

>On Mar 13, 2006, at 20:24, Res Pons wrote:
>
>>I hope soon there's a server side control feature for this.
>>Setting auto props per user just doesn't make any sense to me and
>>if user set their own, wouldn't there be a conflict? I tried to
>>implement this feature on my server and I was told it yet doesn't
>>exist or not possible.
>
>What do you mean, "if user set their own, wouldn't there be a
conflict"?
>
>I would suggest that you have a config file which specifies the
>automatic properties you want. Distribute this to all users. Then
>have a pre-commit hook which rejects files which do not have the
>required properties. Then there can be no problem.
>
>Well, of course there can be a problem of a user needing to work with
>two different repositories which have two different auto-props
>policies. That's not handled well right now. Sure, you can tell the
>svn command to use a different config file, but it's tedious and
>error-prone to specify that for each and every svn command.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 15 02:40:51 2006

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