yao-msft
yao-msft
> If the PackageVersion is greater than the display version, even assuming uniqueness of display versions, the package would still be listed for upgrade I think with PackageVersion mapping feature,...
> Ahhhh, I see. Why are portable apps excluded from version mapping? I think it's because winget is acting as the installer for the portables, winget controls what registry values...
> I think it is an issue with disambiguating between `voidtools.Everything` and `voidtools.Everything.Lite` and `voidtools.Everything.Alpha` In that case, I think `winget upgrade voidtools.Everything -e` would work.
I would say for this one, it's not actually "bypassing", we still perform the check but "ignore" the results.
> > Understandable. When --force was changed to no longer be the hash override, though, it no longer requires an admin setting. I can certainly see value in adding it,...
@Trenly as fyi, all group policy values and strings will need to be reviewed by some Microsoft internal team, so these naming/description may need to be changed after review (we'll...
This package selection mechanism could be extended to `winget upgrade `, `winget uninstall ` and `winget show ` as well, since these use the same worflow to pick a package...
> @yao-msft So maybe something like adding "--prompt" could prompt if the results are ambiguous, and a setting could be added to make the setting default and "--no-prompt" could override...