[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Size of TSVN msi installer, need your opinion

From: Oto BREZINA <otik_at_e-posta.sk>
Date: Sun, 13 Sep 2015 12:34:59 +0200

On 2015-09-12 11:03, Stefan Küng wrote:
> Hi,
> [SNIP]
> So, what should I do?
> Link everything statically and have the msi use almost 40MB for a download?
> Or go back to linking dynamically to the c-runtime, but not include the
> merge modules (as I said: they're broken). That would require that all
> users install the c-runtime distributable manually. If the runtime is
> not installed, then TSVN would throw errors and would not start.
> Opinions?
I'm running WIN10 on work notebook I do use 90% time, where everyting
works ok, (c-runtime) auto installed.
So smaller installer would be better here, but no big difference.

I do centralized distribution over GPO, having add depencies is not that
big issue as long as they got MSI, what seems be not a case here.

Interesting story is first affected was secretary, who don't use TSVN at
all, but i was too lasy to create group removing just this one PC and I
want to have all PC have all common SW, so you can log and work anywhere.

To make it work a used psexec to run c-runtime installer on all
machines, what is bit pain, but was not that bad.

In this case I download installer only once, and I don't care it is 20,
40, or 140 MiB ...

This make to vote for static link.

If installer can report missing depencies, as it can't install that
would be good too.

I'm not using WIX, but c-runtime running installer exe as part
installation should work too instead of merging. Or did I miss
understand here something?

> Stefan


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-13 12:35:26 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.