You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think adding a page describing installation locations would be appropriate.
It probably should start off with a snippet describing the difference between a package and the software a package installs.
Then describe where packages get installed to (e.g. under $env:ChocolateyInstall\lib)
Then describe where portable software gets installed (In the lib folder or in Get-ToolsLocation normally)
Then talk about various installation type packages, and how to find where installers put the software (like the Software installed to... message)
And discuss template and extension package install locations
And cover packages that don't install any software (meta packages, configuration changes), or where there is not a simple installation location (windows update packages)
Why Is It Needed?
I have seen a number of issues/comments/discussions in various places with people having difficulty finding where a package actually put the software, in many cases stemming from not fully understanding how Chocolatey packages work. chocolatey/choco#1929
Additional Context?
This should go alongside changes to help people find the installation location after the package is installed:
What New Or Updated Would You Like To See?
I think adding a page describing installation locations would be appropriate.
$env:ChocolateyInstall\lib
)Get-ToolsLocation
normally)Software installed to...
message)Why Is It Needed?
I have seen a number of issues/comments/discussions in various places with people having difficulty finding where a package actually put the software, in many cases stemming from not fully understanding how Chocolatey packages work. chocolatey/choco#1929
Additional Context?
This should go alongside changes to help people find the installation location after the package is installed:
choco info
output choco#1901The text was updated successfully, but these errors were encountered: