To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=74914 Issue #|74914 Summary|Reusing old 8.3 names and File Table Keys as in a prev |ious MSI installer Component|Installation Version|OOo 2.1 Platform|All URL| OS/Version|Windows, all Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|PATCH Priority|P3 Subcomponent|code Assigned to|of Reported by|tml
------- Additional comments from [EMAIL PROTECTED] Tue Feb 27 13:49:41 +0000 2007 ------- This problem occurs especially when building multi-language Windows Installer (MSI) installers, but could well occur also with just single-language installers, although not to the same extent. We want to support upgrading from one installed version of OOo to another using Windwows Installer Patching and Upgrading (.msp files). For this to work smoothly and the .msp files to be as small as possible, it is essential that a file has the same key (FTK = File Table Key) in both the old and new MSI database. Currently the Perl scripts in OOo that built the MSI database just make the FTKs unique by incrementing and suffixing a counter when files with the same basename occur in different folders. Especially if the new and old MSI database have different language sets, this leads to the situation that the same FTK in the two databases refer to different files. The patch generating msimsp program doesn't understand this, and is not capable of generating a (binary) diff for the file in question, but includes it as a whole. A similar situation exists for the 8.3 "short" names for files and folders. Currently just a running counter is used to generate those. The problem described above is not restricted just to the multi-language installers that Novell builds. It can occur also with single-language MSI databases, if a file with the same basename as an existing file is introduced in the new version. To fix this problem, we add the possibility to pass an environment variable "PREVIOUS_IDT_DIR" that points to the folder from the old build where the .idt files are. If this environment variable exist, the old File.idt and Director.idt files are read and a couple of mapping tables initialised from them. When the FTK keys and 8.3 names are generated, the Perl code first checks if there are saved mappings from the old database, and uses those. Patch will follow. --------------------------------------------------------------------- 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]
