I think it is better to renew the installer completely. I have found a open source framework that simplifies the creation of the installer and builds the msi file for us. It offers .net framework for writing a installer screens (MSI does not provide such a thing). The tutorials I have read looked pretty streight forward, at least for the standard installer stuff.
I think I read that you can include a dependance msi package in the msi package. But I forgot again. I looked into msi a month ago. The last month has been quite intense for me. We could deliver a single MSI file in future and even create the patch file from it. I am currently unsure concerning the package signing, but once we have a pure MSI setup it should be easy to add too, right? Am 3. März 2018 16:55:32 MEZ schrieb Pedro Lino <pedro.l...@mailbox.org>: > >> Technically seen: >> To unpack the installation files and to start the installation >with MSI. >> >> Historically seen: >> I don't know! ;-) >> > > >The nsis installer extracts and runs the MSVC runtime libraries >installer before running the AOO installer. Since AOO is compiled with >MSVC it requires these libraries are installed first. I don't know how >TDF got rid of that step but possibly they are including the MSVC >libraries needed in the program folder? > > >Maybe AOO can do the same and skip the nsis installer? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
