Ingo Schmidt írta:
It should be no problem, to change this number to a more useful versioning schema. We only have to guarantee, that it is increased for Major Upgrades. And it should be also simple to use the MsiFileHash table.

It would be nice, if we could work together, to find a solution for usable OOo patches using Windows Installer techniques. Until now, I have only seen Windows Installer patches for OOo, that were created by commercial tooling. But here we need a process, that can create msp files automatical and reliable within this Perl packaging process.

Greetings

 Ingo

As I saw in InstallShield Developer and Professional they create patches from latest final binary installer and older installers (one or more)... So we might want to follow this way. We should look the size of update packages what is enough for us version by version updater or incremental updater (with all version's patches included)...

I found this:

MSIDIFF

MSIDIFF can dump complete or compare two Windows Installer databases as well as patches and transforms, it installs shell extensions (right click on file) to simplify this but it can also be used from the command line.
The output can also be fed back into the MAKEMSI tool which was also written by Dennis Bareis, allowing you to automate and changes you may have made using a table editing tool such as Orca.

WWWWeb Site

http://www.installsite.org/pages/en/msi/updates.htm


KAMI


Reply via email to