(#1485) Display package source during install/upgrade #3267
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description Of Changes
This logs the package source uri to info before downloading nupkgs
during both install and upgrade. Additionally, it debug logs the
download URI that the nupkg available at.
The information outputs for both individual package installs/upgrades,
and for dependencies that get installed/upgraded by their parent
package. This information is especially useful when multiple sources
are in play, so the user can determine where individual packages
are coming from.
Motivation and Context
See #1485
Now that Chocolatey CLI is using NuGet.Client libraries, this was trivial to implement.
Testing
See added NUnit tests for installing/upgrading from a local source.
For remote sources:
.\choco.exe install wget --force --skip-powershell --debug
.\choco.exe upgrade wget --force --skip-powershell --debug
.\choco.exe install dotnet-all --force --skip-powershell --debug
Operating Systems Testing
Change Types Made
Change Checklist
Related Issue
Fixes #1485