On Oct 22, 2008, at 13:58, Bill Hoffman wrote:
> We are using commit checks to make sure mime types are set
> correctly in our repository. This works great. However, it means
> that each client must have a correctly configured client.
>
> Basically something like this:
>
> UNIX ~/.subversion/config
> Cygwin ~/.subversion/config
> Windows ~/Application Data/Subversion/config
>
>
> The problem is that this config file is not under version control!
> Each user has some random copy of it from when they installed svn.
> There is no way to update this file for all of the users other than
> sending out an email.
>
> There should be some way to store this file in the repository
> itself. Maybe svn could first look here:
> UNIX ~/.subversion/config
> Cygwin ~/.subversion/config
> Windows ~/Application Data/Subversion/config
>
> Then append anything it found in the root of the project tree with
> the name config. Basically, this information should be part of the
> project or repository. I maybe missing something. Is there a
> better way to do this?
You are welcome to put that file or any other file into your
repository and instruct your users to run "svn up" on the config
directory on occasion.
> Right now we have a wiki entry that has a list of mime types that
> you have to copy into your config file. Almost without fail each
> new user forgets or mis-configures the file. Then things become a
> mess.
But you have a pre-commit hook that ensures things that come into the
repository have the right properties, yes? And if not, it prints an
error message to the user? The message to the user can tell them what
to do to fix it, be that manually copying data from a wiki page into
their config file or running "svn up" on their config directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-23 00:41:00 CEST