Molle Bestefich wrote:
> Björn Eriksson wrote:
>
>>Q: can we make the check-for-update URL configurable? I'd very much like
>>to point it to a server of my own. My current procedure is to ask all new
>>developers *not* to download tsvn themselves. This works sometimes... :/
>
>
> Registry, right, not user-visible configuration?
In my view, the only situation to use this is a corporate deployment,
where one person is keeping track of release stability, and decides when
to upgrade. I didn't test it yet, but presumably the way this should
work is this person downloads the MSI, uses Orca to add in this registry
key setting, and ensures all users install from this MSI. So no users
need to set this key, it is in their installer MSI.
This feature will really help our situation, where I need to keep about
40 users updated.
> There's a (rather large) bit missing before it's good for corporate deployment:
> How do you forcibly downgrade your clients to an earlier version?
The need for this will be mitigated (though not eliminated) by having
one person manage what releases get put on the private update URL, so
there's less chance of a "bad" release getting installed.
-Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 25 23:16:47 2005