Confirmed users
201
edits
(Created page with 'Plan for the Windows Installer (MSI) packaging of Firefox and other toolkit apps. = Bugs = Current work is proceeding in [https://bugzilla.mozilla.org/show_bug.cgi?id=231062 …') |
m (→L10n) |
||
Line 35: | Line 35: | ||
*Use MST files (transforms) to transform the en-US MSI into an ab-CD MSI. This would require generating a transform, which WiX seems to provide no way to do that does not involve already having the ab-CD MSI in hand. There are ways to create the MST with VBScript automation and other stuff, but I'm not terribly keen on that. This also has the disadvantage of shipping both the en-US and ab-CD locale files with every localized installer (I am not aware of any way to remove files through an MST) | *Use MST files (transforms) to transform the en-US MSI into an ab-CD MSI. This would require generating a transform, which WiX seems to provide no way to do that does not involve already having the ab-CD MSI in hand. There are ways to create the MST with VBScript automation and other stuff, but I'm not terribly keen on that. This also has the disadvantage of shipping both the en-US and ab-CD locale files with every localized installer (I am not aware of any way to remove files through an MST) | ||
*Package the nonlocalized components of the build into a wixlib (essentially a giant object file) and then build each locale separately from the wixlib. This requires some work on releng's part to pull out the wixlib and then build all the other locales on top of it, though probably not significantly more than repackaging already takes. | *Package the nonlocalized components of the build into a wixlib (essentially a giant object file) and then build each locale separately from the wixlib. This requires some work on releng's part to pull out the wixlib and then build all the other locales on top of it, though probably not significantly more than repackaging already takes. | ||
I definitely prefer the second option. |