Bug 160979

Summary:	WiX packaged MSI installer offering only LO "program" and "font" for custom install
Product:	LibreOffice	Reporter:	V Stuart Foote <vsfoote>
Component:	Installation	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	cloph, vsfoote
Priority:	medium	Keywords:	difficultyMedium, needsDevEval, skillPython, skillWindows
Version:	24.8.0.0 alpha0+
Hardware:	All
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	160978
Attachments:	Clip of options panel of an msiexec install of the TB78 20240507 WiX build

Description V Stuart Foote 2024-05-07 16:48:11 UTC

Current Jenkins TB78 Windows build with WiX packaging [1] does not provide customization option selections available with Cygwin msitools based builds.

Typical msiexec.exe /a Administrative installs for testing not affected, but doing actual /i installs are uncomfortable with the package as is. Expect also we'll need to test the optional features with the WiX packaging get laid down correctly.

=-ref-=

[1] https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb78-pollux-TDF_wix/

Comment 1 V Stuart Foote 2024-05-07 16:50:05 UTC

Created attachment 194017 [details]
Clip of options panel of an msiexec install of the TB78 20240507 WiX build

Comment 2 Jussi Pakkanen 2024-05-07 17:22:48 UTC

The reason it has only those two was that originally it was meant to illustrate how things can be split into selectable packages. Once that was done there was nothing more to do as we had to wait until upstream took care of all the CI work and so on.

There was also some discussion that maybe the installer should not even provide selectable options. The macOS installer does not do that either and it would simplify the implementation. But that is a policy decision for other people to make.

Comment 3 Christian Lohmaier 2024-05-23 12:33:37 UTC

guess the bug can be set to new/confirmed - but then again that is certainly not my personal focus/don't take that as me working on it.
Besides not offering the different categories/optional component it also needs some core changes to use multiple cabs for example to be able to handle all UI langauges. I guess you can consider parts of that easyhack territory.

Depending on what level you want to work on it can be easy to medium to interesting....

a "proper" way is to use the information from scp2 project and create the split based on that, like the current msi creation does (and also what is used to define the macos or linux packaging) - adding skillWindows since there's little point for users not having access to windows to work on this, although no special knowledge of Windows is necessary.

There's some basic examples of different components as mentioned, but the way those work currently is a little "ugly" - we have nice instdir where deliverables are placed already, but the WiX packaging rips that apart to package the individual parts - OK for demonstrating the different components, but ideally it should work straight from the instdir.