Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pin versions by Semantic Version number range #284

Closed
2 tasks done
davidem00 opened this issue Nov 17, 2023 · 3 comments
Closed
2 tasks done

pin versions by Semantic Version number range #284

davidem00 opened this issue Nov 17, 2023 · 3 comments
Labels
Duplicate Issue Issues that are duplicates. Wrong Repository A ticket tied to the wrong repository would receive this label.

Comments

@davidem00
Copy link

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

currently can only restrict installations to specific versions, as opposed to version ranges

in one case, may possess a license only for v3.x of a product (with any minor version upgrades included), but v4.x has also been released on its own maintenance path

also allows for automatic installation/upgrade of broken packages once a known good version becomes available, skipping any auto-packaged versions beforehand

Describe The Solution. Why is it needed?

allow pins to specify ranges (maybe with wildcards).
allow upgrade command to operate within a range, but be ignored outside of it

Should allow specification covering versions that aren't necessarily installed yet

Additional Context

e.g.
:: skips any subsequent updates until v4., say, for a product that is broken for a given version range
choco pin add -n igdm --version="'>4.
"

:: allows installation/upgrade of subsequent packages for applicable Major version
choco pin add -n beyondcompare --version="'<4.0'"
(alternatively)
choco pin add -n beyondcompare --version="''3.*'"

Related Issues

No response

@TheCakeIsNaOH
Copy link
Member

This is a duplicate of chocolatey/choco#1278

@davidem00
Copy link
Author

davidem00 commented Nov 17, 2023

Lol. I searched through Open issues for "pin" before posting mine, and only two came up, not including this one. Hard to guess what words should be wildcarded in a search but I figured the command name wouldn't be one of them.

The funny part is the OP being motivated by the same product that I am : beyondcompare

@davidem00
Copy link
Author

Oh, I see. It's in the "choco" repo, not "home". ffs. No good deed...

@davidem00 davidem00 changed the title pin versions by numeral range pin versions by Semantic Version number range Nov 17, 2023
@pauby pauby closed this as not planned Won't fix, can't repro, duplicate, stale Dec 23, 2023
@pauby pauby added Wrong Repository A ticket tied to the wrong repository would receive this label. Duplicate Issue Issues that are duplicates. labels Dec 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Issue Issues that are duplicates. Wrong Repository A ticket tied to the wrong repository would receive this label.
Projects
None yet
Development

No branches or pull requests

3 participants