Major+Minor Package Version Resolution

[kbrowns]

We're making heavy use of chocolatey with Artifactory as the backend package store and it's working swimmingly. We have one scenario that I've yet to figure out to my liking. I suspect this is a nuget protocol limitation, but thought I'd start my search here first. When I do this:

choco install -y foo

I get the latest version (16.2.0.100) pulled down and installed. Wonderful - Build 100 is the last build of our 16.2 release which is our greatest release. When I do this:

choco install -y foo --version 16.1

It fails - as expected (because there is no version 16.1.0.0 of foo). Is there some mechanism I can use to ask for the great version of a package within a major/minor?

[ferventcoder]

@kbrowns right now, this would be a feature request.

[ferventcoder]

Related to #800 and #1278

[ferventcoder]

related to #1874

[timhunt]

I know it is not very helpful to add comments to issue trackers when you are annoyed, but ...

OK, so the purpose of Choclately is to make it easy for users to managed the software packages installed on their computer. So far, so awesome.

But, what I want to do right now, which should be easy, is Install the latest PHP 8.1". I have read this, and the related issue, and it is not easy.

I think what I need to do is:

1. choco search --exact --all php - to find the latest version of PHP.
2. Then the relevant choco upgrade command.

Point 1: It would be nice if the choco upgrade and choco install documenatation page told you that command to find the available versions. I mean, I can spend 10 minutes search stackoverflow and going round in circles to find that, but it would be better user experience if I did not have to.

Point 2: When I run that, it lissts 210 PHP versions going back to 5.3.6, but not including anything more recent than 8.0.17, so that does not help. In contrast, choco search php lists PHP 8.2.6. What?!

Point 3: `choco search' not helpful at all, nor goole searching for the answer. (Removing the --exact option stops it listing any PHP versions. What?!)

Point 4: Is it really helpful that every page of the chocolatey docs with starts with over a screenful of stuff I don't care about relating to deprectation?

OK, I give up https://community.chocolatey.org/packages/php#versionhistory. At least that exists.

Hopefullly there is some useful feedback burried in there.

[pauby]

@timhunt Sorry you're having a tough time.

Point 1: It would be nice if the choco upgrade and choco install documenatation page

Without sounding flippant, that's not the goal of those pages. They are to describe upgrade and install functionality.

Point 2: When I run that, it lissts 210 PHP versions going back to 5.3.6, but not including anything more recent than 8.0.17, so that does not help. In contrast, choco search php lists PHP 8.2.6. What?!

I ran choco search --exact --all php and 254 packages were returned, with the latest being 8.2.6:

You may have hit a caching issue if you didn't get that.

Point 3: `choco search' not helpful at all, nor goole searching for the answer. (Removing the --exact option stops it listing any PHP versions. What?!)

choco search php returned 48 packages for me.

Point 4: Is it really helpful that every page of the chocolatey docs with starts with over a screenful of stuff I don't care about relating to deprectation?

Without being flippant (again) we wouldn't add it if we didn't think it is helpful. This potentially breaks things for some people, and while I appreciate it won't for you, it may for others. We want to make sure those people are as informed as they can be about this stuff. That's why we have put it on plenty of pages.

Once the deprecation is old news, we'll remove it.

[timhunt]

Thanks for the speedy respnse.

I agree that it is not the purpose of the upgrade docs to describe choco search. However, it is the purpose of that page to describe the use of the --version option, and telling you how to find the version number you need would be valuable docs (even if it just says "You can find the avilable versions of a package using choco search, for example choco search --exact --all ." I mean, at the moment, there are more verbose about hundreds of other options, like checksumtypex64, and hardly anything about this vital option that is essential to the use of this commant.

Telling me I have "hit a caching issue" without telling me what to do about it is unhelpful. Can you suggestion something actionable? Thanks.