Version specifiers

[jayvdb]

choco packages have some rather strange versions at times. Most people dont want to put patch numbers into a package.json or similar. They expect those to be handled in a lock file.

And often one wants updates, but only to the same minor release, but not the next major, so ideally something like ~1.2 is supported.

When I tried to specify just 3.1 for a package without a 3.1*, I get

Installing R.project (3.1) > failed
Chocolatey v0.10.11 Installing the following packages: R.project By installing you accept licenses for the packages. R.project not installed. The package was not found with the source(s) listed.  Source(s): 'https://chocolatey.org/api/v2/'  NOTE: When you specify explicit sources, it overrides default sources. If the package version is a prerelease and you didn't specify `--pre`,  the package may not be found. Version was specified as '3.1'. It is possible that version   does not exist for 'R.project' at the source specified. Please see https://chocolatey.org/docs/troubleshooting for more   assistance.  Chocolatey installed 0/1 packages. 1 packages failed.  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).  Failures  - R.project - R.project not installed. The package was not found with the source(s) listed.  Source(s): 'https://chocolatey.org/api/v2/'  NOTE: When you specify explicit sources, it overrides default sources. If the package version is a prerelease and you didn't specify `--pre`,  the package may not be found. Version was specified as '3.1'. It is possible that version   does not exist for 'R.project' at the source specified. Please see https://chocolatey.org/docs/troubleshooting for more   assistance.

When I tried to specify just 7.3 for php, I got an error about it being less than the installed 7.3.6

Using ^:

Chocolatey v0.10.11 Installing the following packages: php By installing you accept licenses for the packages. '^7.3' is not a valid version string. Parameter name: version

[jayvdb]

chocolatey/choco#800 and chocolatey/choco#688 and chocolatey/choco#1278 will help.

But this could be done within Fudge by getting the version list and then selecting the appropriate version.

[Badgerati]

If we do this in Fudge, much like those issues referenced, I would prefer to follow nuspec versioning.

This, in theory, shouldn't be too hard - just a bit a regex, and calling --all on choco 🤔

Something like: choco search curl --all --exact for curl.

[jayvdb]

Sounds good.