Repository navigation
[Zip] Nested Installer Files Validation #2523
Description
- Non-Portable Installer Type doesn't warn when
PortableCommandAliasis included for a NestedInstallerFile
Note: The below items are likely not implemented yet, as Portable support hasn't been implemented for Zip files yet. I'm placing them here as a consideration to ensure they are validated against
- Portable Installer Type doesn't throw an error when two entries have the same
RelativeFilePath- This might be acceptable as long as they have different command aliases?
- Portable Installer Type doesn't throw an error when two entries have the same
PortableCommandAlias
Activity
denelon commentedon Sep 19, 2022
Ryan (@ryfu-msft) please take a look at this.
ryfu-msft commentedon Sep 20, 2022
Thanks for catching this, additional validation will be added in #2500
sitiom commentedon Jan 26, 2023
Seems like this isn't implemented: microsoft/winget-pkgs#94699 (comment)
denelon commentedon Jan 26, 2023
This version isn't in the validation pipelines yet. We're waiting for the 1.4 client rollout to the majority of users. We want to avoid as much confusion as possible with the "winget" source having .zip-based packages they can't install with earlier versions of winget.
sitiom commentedon Jan 26, 2023
What I mean is that
winget validatefails locally and that an exception should be made for the sameRelativeFilePathbut differentPortableCommandAlias.denelon commentedon Jan 26, 2023
Ryan (@sitiom) can you create a new issue with an example?
sitiom commentedon Jan 26, 2023
#2884