Re: "System-wide configuration area" and global-ignores

Ok, Ryan's email seems like it may clear up a lot of my confusion, but I'll
need a little more time to digest and research this stuff.

At 11/16/2005 09:27 AM, Ryan Schmidt wrote:
>You can set up a client configuration file as you like, with the set
>of global ignores, auto-props and other settings recommended for your
>organization, and distribute it to all developers via email, web
>page, file sharing volume or whatever.

This concerns me. Does this mean that I can't reliably control any client
behavior with some "master" server configuration that can not be overridden
(if desired)? Configuration control is done primarily through client
config files?

And if so, are these client config files consistent across clients (eg,
different svn cmdline revs, TortoiseSVN, others)? What are these files?

>If you want to prevent anyone from committing, for example, *.o files
>to the repository, you can write a pre-commit hook that gets a list
>of all files in the transaction, does pattern matching on them to see
>if any prohibited files are listed, and if so, outputs a message to
>that effect and exits with a nonzero code, which cancels the commit.
>The user then corrects the problem and attempts the commit again.

I suppose this is the only server-side "master" control to do what I seek?

-Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 16 16:52:39 2005