Bug 141993 - Parent component doesn't include the size of the child components while custom setup
Summary: Parent component doesn't include the size of the child components while custo...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
7.1.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-30 13:04 UTC by Vadym
Modified: 2021-04-30 14:02 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Parent component doesn't include the size of the child components while custom setup (72.34 KB, image/png)
2021-04-30 13:05 UTC, Vadym
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vadym 2021-04-30 13:04:31 UTC
Description:
Parent component doesn't include the size of the child components while custom setup

Steps to Reproduce:
1. Run LibreOffice_7.1.2_Win_x64.msi
2. Click "Next" button
3. Select "Custom" setup and click "Next" button
4. Select "Optional Components" or "Dictionaries" or "User Interface Languages"

Actual Results:
"Optional Components", "Dictionaries" and "User Interface Languages" doesn't show the size of the components that are included.

Expected Results:
"Optional Components", "Dictionaries" and "User Interface Languages" show the size of the components that are included.


Reproducible: Always


User Profile Reset: No



Additional Info:
It's installation testing.
Comment 1 Vadym 2021-04-30 13:05:52 UTC
Created attachment 171528 [details]
Parent component doesn't include the size of the child components while custom setup
Comment 2 Mike Kaganski 2021-04-30 14:02:44 UTC
This is the feature of Windows Installer, which provides separate numbers for feature and subfeatures. The strings used for that (SelChildCostPos, SelChildCostNeg, SelParentCostPosPos, SelParentCostPosNeg, SelParentCostNegPos and SelParentCostNegNeg) are documented in [1].

A hack that could be used to implement this is described in [2]. But I doubt that it's useful. The separate numbers are designed by MS specifically this way; and using subfeatures size as component size (as [2] suggests) is not correct, since some features may have own size, and showing subcomponents size would not include the main selection size (so a string like "this feature requires 200 KB; its subcomponents need 150 KB" would be shown "this feature and its subfeatures require 150 KB").

This is NOTABUG, since this works as intended and provides correct information.

[1] https://docs.microsoft.com/en-us/windows/win32/msi/selectiontree-control
[2] http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Feature-costing-td1307593.html