The MSI feature structure should differentiate between the LibreOffice suite (root feature) and all other features as children, with addition of a common files feature and a redistributable dependencies feature. The common files would be shared dependencies of at least two program modules, with the condition for installation being '($program_module=2 OR ?program_module=2) OR ($other_program_module=2 OR ?other_program_module=2)' - where any of the dependent program modules are installed.
(In reply to Matthew Millar from comment #0) > The MSI feature structure should differentiate between the LibreOffice suite > (root feature) and all other features as children, with addition of a common > files feature and a redistributable dependencies feature. > > The common files would be shared dependencies of at least two program > modules, with the condition for installation being '($program_module=2 OR > ?program_module=2) OR ($other_program_module=2 OR ?other_program_module=2)' > - where any of the dependent program modules are installed. I'm not very familiar with the MIS structure. Can you point me at some docs about how the file should be laid out/best practices? Thanks! Status -> NEEDINFO
Editing of MSI tables can be done with Microsoft's ORCA for testing. ultimately though, the MSI generating script needs to be updated for this to be automated. MSI feature structure --------------------- - [Features][1] define high-level products and grouped functionality which are parents to Sub-features which are 'modules'. - [sub-]features reference [components][3] (families of [files][4] which make up the modules). - The association of [sub-]features and components is handled in the [FeatureComponents][2] table [1]: https://msdn.microsoft.com/en-us/library/aa368585(v=vs.85).aspx "MSI Feature table" [2]: https://msdn.microsoft.com/en-gb/library/aa368579(v=vs.85).aspx "MSI FeatureComponents table" [3]: https://msdn.microsoft.com/en-us/library/aa368007(v=vs.85).aspx "MSI Component table" [4]: https://msdn.microsoft.com/en-us/library/aa368596(v=vs.85).aspx "MSI File table" Component installation conditions --------------------------------- [Conditions][5] for installation of components (families of files, e.g. modules), subject to the installation action for the containing feature. - The ['State Value'][6] conditions suggested in my original post [5]: https://msdn.microsoft.com/en-us/library/aa368012(v=vs.85).aspx "MSI Conditional statement syntax" [6]: https://msdn.microsoft.com/en-us/library/aa368012(v=vs.85).aspx#Feature_and_Component_State_Values "MSI Conditional state values"
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
hi Matthew, would you please explain in simple words what would be the benefit of this? I'm not a developer but just a simple user.
status -> NEEDINFO please Matthew answer to comment 4