-
Notifications
You must be signed in to change notification settings - Fork 905
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
Include software install path in choco info
output
#1901
Comments
...or maybe a new command such as "diags" that could display choco version info, install location, Chocolatey cache location, nuget cache location, configured features (not a list of all of them), system state, validation checks, a quick check and report that the CRCs are OK on all Chocolatey files, a quick ping to the configured sources, etc. |
@bcurran3 anything giving the information required is appreciated. But I think the info command is more intuitive. If I'm not mistaken HomeBrew does the same. |
I think I misunderstood. I was thinking more upstream and about Chocolatey versus just a single package. I guess my suggestion is a completely different one. I'll create a new issue. Done: #1903 |
My use-case (problem) was I installed irfanview on a brand new Win 10 machine, but it's not in Program Files, I can't find it in the start menu (search results send me to the Web), etc. I know if you're clever you realize all things get installed in the secret choco place, but I can't remember what that is and expected it to come out of an |
Displays the saved software installation location for info and list commands. If the package has no software install location, it displays nothing, and if the package was installed/upgraded before the saving feature was added, again, it does not show that line.
Displays the saved software installation location for info and list commands. If the package has no software install location, it displays nothing, and if the package was installed/upgraded before the saving feature was added, again, it does not show that line.
Displays the saved package deployment location for info and list commands. If the package has no deployemnt location, it displays nothing, and if the package was installed/upgraded before the saving feature was added, again, it does not show that line.
(#1901) Display software installation location
choco info
output
choco info
outputchoco info
output
Unfortunately, I am going to have to re-open this issue, as it will not be possible to bring this change in at present. This change, while small and which builds on this issue, can't be implemented fully in Chocolatey Licensed Extension without changing the dependency on the Chocolatey package. This is not something we are planning in this release, so this change will be reverted and will be re-added in the next release. Apologies on this. Please let me know if you have any questions. |
Based on some testing that was completed, we can't bring in this change currently, since we can't provide the same functionality in CLE without bumping the version number of the CLI dependency in the nuspec file. This is not something that we are ready to do, so taking out this change, and the issue will be moved to the next milestone.
* release/2.3.0: (153 commits) (#23) Move call to SetRemotePackageNamesIfAllSpecified (#1901) Revert commit to display location (maint) Update Authenticode Signature (tests) Some minor tweaks for test consistency (#310) Set-EnvironmentVariable: delete values properly (tests) Remove v2 import tests (#310) Fix test issues (#310) Fixup v2 compatibility (tests) Working on tests during pairing session (#2050) Add Pester test for --ignore-pinned option (#3381) Add Pester tests for rule command (#1144) Add Pester test to cover hash validation (#72) Add Pester tests to cover new functionality (test) Update assertions for push commands (#1310) Add Pester test to validate output (#23) Add tests to handle install all (#2200) Add test for new enhanced exit code (#1764) Add test for new enhanced exit code (#1760) Add test for new enhanced exit code (#1759) Add test for new enhanced exit code ...
* master: (37 commits) (#310) Fix path to chocolatey.lib files (maint) Corrected casing of file (#23) Move call to SetRemotePackageNamesIfAllSpecified (#1901) Revert commit to display location (maint) Update Authenticode Signature (tests) Some minor tweaks for test consistency (#310) Set-EnvironmentVariable: delete values properly (tests) Remove v2 import tests (#310) Fix test issues (#310) Fixup v2 compatibility (tests) Working on tests during pairing session (#2050) Add Pester test for --ignore-pinned option (#3381) Add Pester tests for rule command (#1144) Add Pester test to cover hash validation (#72) Add Pester tests to cover new functionality (test) Update assertions for push commands (#1310) Add Pester test to validate output (#23) Add tests to handle install all (#2200) Add test for new enhanced exit code (#1764) Add test for new enhanced exit code ...
This reverts commit c74a19c.
…evelop * 'develop' of https://github.com/josh-cooley/choco: (145 commits) (maint) Add CODEOWNERS files (build) Add templated notifications to all builds (build) Add verification of source scripts (doc) Further tweak docgen for Chocolatey.PowerShell (doc) Tweak docgen for Chocolatey.PowerShell (chocolatey#3446) Update GenerateDocs.ps1 (chocolatey#3307) Do not create Tools directory from MSI (maint) Do not create Chocolatey directory in MSI (chocolatey#310) Fix path to chocolatey.lib files (maint) Corrected casing of file (chocolatey#23) Move call to SetRemotePackageNamesIfAllSpecified (chocolatey#1901) Revert commit to display location (maint) Update Authenticode Signature (tests) Some minor tweaks for test consistency (chocolatey#310) Set-EnvironmentVariable: delete values properly (tests) Remove v2 import tests (chocolatey#310) Fix test issues (chocolatey#310) Fixup v2 compatibility (tests) Working on tests during pairing session (chocolatey#2050) Add Pester test for --ignore-pinned option ...
This reverts commit c74a19c.
Following this tweet, it would be great if the installation folder could be inquired somehow. For example, the command
choco info packageName
could also report the path.The text was updated successfully, but these errors were encountered: