Svn – Subversion – Can I set auto-props on the server side

mimesvn

I'm maintaining a SVN server and on user needs to commit many adobe illustrator files (ie *.ai). I can use the auto-props in their config to set it as a binary file so that it won't be in the mailing list commits. However I'd like to make this as easy as possible. Is there something I can set in the SVN server config, so that it (ie the server) will automatically set the correct svn:mime-type?

Best Answer

It's not possible. There is a long standing feature request for broadcasting configs to client. It's not presently due until 2.0, or later.

The closest you can come is to use hooks. Either with a pre-commit to prevent incorrectly configured clients from submitting the wrong data. Or a post-commit to retro-fix wrong data.

Neither is great and I believe the latter is even advised against.

Related Solutions

Svn – Setting up Subversion Lock-Modify-Unlock on Windows Server

I think your issues are with VisualSVN, you need to contact them to configure the product to not show the dialog and to automatically unlock on revert. Stefan is quite good about making fixes, and it sounds like the no-unlock config item should also apply to revert as well as commit. Note that the revert functionality does not contact the server, so he might consider that an undesirable change.

In most cases the lock is a manual thing you need to explicitly lock and unlock, so most people using it would want to have to ensure they unlock.

If the 'lock dialog' is a Tortoise thing, you can configure the dialogs to auto-close if there's no errors. Again, send a message to the mailing list to see if everyone else wants this change.

PS. When I converted to SVN from VSS, I decided to go with the copy-merge-modify approach, and then slap locks on everything if it didn't work out well. Nobody has complained, and they all like the system (once I'd told them not to try resolving conflicts with binary files)

Svn – from svn to git (+ LDAP + password-less updates + passworded access control)

If you still prefer using svn up for live site, read svn help up carefully and pay attention on some options in order to handle credential in the Smart Way

Global options:
  --username ARG           : specify a username ARG
  --password ARG           : specify a password ARG
  --no-auth-cache          : do not cache authentication tokens

Best Answer

Related Solutions

Svn – Setting up Subversion Lock-Modify-Unlock on Windows Server

Svn – from svn to git (+ LDAP + password-less updates + passworded access control)

Related Topic