-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add version constraints #7
Comments
Ideally this would be done in tandem with native Chocolatey support for this kind of thing. However, in the interim it's plausible a "good enough" solution can be added to this module to bridge the gap. I'll mark this up for grabs for now in case other folks want to have a stab at it before one of us gets around to it, but I'll make a note to check back and see what an implementation would look like when I have some time available. 🙂 |
Had an internal discussion with the team. We agree that this collection is probably not the right place to put this logic. As I noted above, this should be supported from the |
I understand, related with chocolatey/choco#800 , 👍 there if interested in this feature and if you can, please help with the impl. Thanks! |
Migrated from ansible-collections/community.windows#39
This is a feature request. I propose to add version range constraint support to accept versions like [7.3, 7.4).
Chocolatey has no native support, hovewer the Chocolatey can lookup all versions like
choco list php --by-id-only -a
(or with `-e switch once chocolatey/choco#1843 is solved). So I propose to allow to specify version by version range constraint, find the latest stable version and then proceed with instal of the discovered/fixed version.The text was updated successfully, but these errors were encountered: