What I imagine is happening is that you have multiple versions of the Windows SDK installed, but winget can only associate one installed app to each package ID, so we don't know which one to pick and return nothing. I think that's a case of us not providing a clear error message. I get "No package found matching input criteria." If version 1.3.0 were released this would also be a valid upgrade.Īdditional example per Having nodejs-lts version 12.1.1 installed and running winget pin -all nodejs-lts -version 12.x should make it so that when later winget upgrade -all is ran it'd check if there is a update available for nodejs-lts what matches 12.x - if the latest update is e.g 16.1.1, but there is also a 12.1.2 it'd update nodejs-lts to that pin add -id "Microsoft.WindowsSDK" If version 1.2.4 were released this would be a valid upgrade. This would pin the version to anything less than version 2. This would pin version to anything less than version 1.3. This would pin to version 1.2.3 and would not be upgraded when any newer version is released. Note: the syntax below is just suggestive.Īssume the user has installed "Awesome App" version "1.2.3". It should also allow users to specify what portion of a version should be pinned so bug fixes could be applied, or even minor version bumps. Pinning should enable users to specify the exact version (likely the default case with no parameters). Additionally, if packages are known to self-update (like Visual Studio Code) an additional meta-data entry in the manifest could help users understand when they may not be able to pin a package.Įdit: Clarifying behavior for ambiguity suggested in other Issues. This might be a function of list or a function of pin. There should also be a mechanism to display the packages (and the version) that have been "pinned". This was mentioned #120 #120 #120 #120 (comment) Proposed technical implementation details (optional) Winget pin and the corollary winget unpin.
Users should be able to prevent the Windows Package Manager from updating a package (assumes the package doesn't have it's own auto-update). Description of the new feature/enhancement
0 kommentar(er)
