To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=74914
------- Additional comments from [EMAIL PROTECTED] Fri Mar 2 13:57:06 +0000 2007 ------- So far I have just created two kinds of .msp patches: Ones that upgrade from several slightly different 2.0.4 builds to one newest 2.0.4 build, and ones that upgrade from one 2.0.4 build to a 2.1.0 build. It should be quite possible to have a .msp patch that upgrades from either 2.0.4 or 2.1 to 2.2. See below for general requirements though. Depending on how many changes there are, and how many upgrade combinations are covered by the same .msp file, it might well be that the .msp file ends up being as big or larger than an installer for the new version, and in that case it obviously makes little sense. For .msp patching to work without requiring access to the original installation source, the installers one is going to enable patching *from* must have included the MsiFileHash table. So it is in general not possible to produce a standalone .msp that would patch some old installation to a newer, if the old installer didn't contain a populated MsiFileHash table. One thing I need to mention is that unfortunately the name of the installation folder must be the same (like "OpenOffice.org 2.0") in both the "old" and "new" versions for patching to work sensibly. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
