[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: Adam D. Walling <adam.walling_at_gmail.com>
Date: Mon, 14 Sep 2015 10:39:14 -0400

Ideally, Microsoft will eventually fix the merge modules, and push the
universal CRT to all windows machines via windows update. I think
bundling the CRT separately is not that much of a pain, and will
quickly become unnecessary. Switching everything else to static link
is a rather large architecture change which may unearth some subtle
bugs. Personally I think keeping the CRT as a separate install is the
right way to go; statically linking everything is only a temporary
workaround which may even be troublesome to revert in the future. But
I don't think the size of the install should factor too much into the
decision either way.

Launching the redist installer itself rather than using a merge module
sounds like a reasonable solution as well, though I am not certain
what logistics are necessary to get that to work smoothly with those
who push the MSI via group policy etc.

On Mon, Sep 14, 2015 at 3:01 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On Mon, Sep 14, 2015 at 4:46 AM, Ben Fritz <fritzophrenic_at_gmail.com> wrote:
>> On Sat, Sep 12, 2015 at 4:03 AM, Stefan Küng <tortoisesvn_at_gmail.com>
>> wrote:
>> >
>> > 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.
>> >
>> Is it possible/legal to distribute the runtime distributable along with
>> TortoiseSVN? The TSVN installer can kick off the runtime installer as part
>> of installation, right? Or would that make the installer even larger than
>> static linking?
> That's what merge modules are for (to include another 'installer' in our own
> msi). Problem is that the merge module is not working as it should. So we
> can not use that.
> Shipping the official c-runtime redistributable installer isn't an option
> either, because that one is different depending on the target OS.
> Stefan
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net

- Adam D. Walling
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-14 16:39:22 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.