You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several packages in the community repository with the installer type currently set to MSI incorrectly. Since the addition of #217 and #220, wingetcreate can now detect when an MSI file is actually built with WIX (thanks @jedieaston!) and will match the WIX installer to the MSI entry. However, this relies on the user to update the installer type themselves, even if wingetcreate can detect it reliably.
As a user, it would be nice if installer types would automatically be updated if the detected installer type is compatible with and more specific than the installer type already defined in the manifest. As an example, InstallerType of MSI could be changed to WIX, but WIX should not be changed to MSI. Similarly, EXE could be changed to INNO, NULLSOFT, or BURN, but not the other way around;
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered:
Trenly
added
the
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
label
Feb 11, 2022
Description of the new feature / enhancement
There are several packages in the community repository with the installer type currently set to MSI incorrectly. Since the addition of #217 and #220, wingetcreate can now detect when an MSI file is actually built with WIX (thanks @jedieaston!) and will match the WIX installer to the MSI entry. However, this relies on the user to update the installer type themselves, even if wingetcreate can detect it reliably.
As a user, it would be nice if installer types would automatically be updated if the detected installer type is compatible with and more specific than the installer type already defined in the manifest. As an example, InstallerType of MSI could be changed to WIX, but WIX should not be changed to MSI. Similarly, EXE could be changed to INNO, NULLSOFT, or BURN, but not the other way around;
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered: