On May 7, 7:49 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> TravisV wrote:
> > In an attempt to get each user to use a standard set of Auto-Prop, we
> > wish to deploy a customized 'config' file as a default to our
> > users.
> > It does seem possible by update the text in "config_file.c" (which
> > contains the default config file text) and then recompiling the msi
> > project. However this seems to be something that would have a less
> > involved solution...
> > Ideally it would also allow for setting Beyond Compare as the default
> > diff tool, and set the "Use Last Commit time" as well...
> > Is there a more elegant way? A command line switch or other ideas
> > which would allow for this update simply in the future? Without
> > rebuilding the project?
> Why don't you just use the registry instead of the config file and
> deploy the settings via GPO?
Thanks for your reply.
Initially registry modifications were considered undesirable. The
primary reason was this, while we are trying to standardize the
behavior of Tortoise across a broad range of new and intermediate
users, some of our more advanced users could easily tailor their
installation's behavior through local update of the config file.
(While technically competent - they are not generally registry editor
types). This is a "Start From Here" approach.
The local file settings do have priority over the registry settings,
which is good, but leads to the behavior of tortoise being defined
from multiple locations (Local file and Registry). If it was all in
the local file, this could be investigated and even diffed against the
standard if a problem with settings was suspected.
Sounds like our options are: 1) Copy the desired file for each install
2) Create a registry insert (via GPO or .exe) 3) Recompile the
Are we thinking about this correctly? or is there options / paths we
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-12 21:55:32 CEST