[Libreoffice] over-long extensions manager list ...

[Tor Lillqvist]

> That is a reason why I suggest to leave the user make its own choice
> among the available dictionaries (only one, all, whatever he want).

Which is exactly what the user can do in a "custom" installation.

> So I restate one of my questions : what is the tool used to code the
> installer ?

A bunch of source data files in scp2 (used on all platforms), a pile of Perl run from solenv/bin/make_installer.pl, a number of template .idt files for Windows Installer, which are then mangled by the Perl code and produces stuff fed to Windows Installer tools like msidb,  ending up with a .msi file, one or several .cab files, and optionally a number of .mst files.

Then there is a setup.exe which is plain C++ code which is a small program that just runs msiexec on the .msi file, telling it which installer UI localisation to use.

And finally all this can optionally be wrapped by NSIS into a single executable file installer like the ones that we offer.

--tml