How to use the command choco info (with examples)

This command allows users to display detailed information about a package with Chocolatey, a package manager for Windows. It provides various options for customizing the information received and the source from which it is retrieved.

Use case 1: Display information on a specific package

Code:

choco info package

Motivation: This use case allows users to retrieve detailed information about a specific package. This can be useful when researching or troubleshooting a particular package.

Explanation: The command “choco info” is followed by the name of the package for which information is desired. In this case, “package” should be replaced with the name of the package being queried.

Example output:

Chocolatey v0.10.15
chocolatey 0.10.15
 GÉANT S.A. <support@softwarecenter.co>
https://chocolatey.org/packages/../license-reconciliation
ChocolateyInstall.ps1 not found. The package will try to use one in its place.
Review the package URL above or in a browser at https://chocolatey.org/packages/chocolatey
To see the total community packages count, run `choco list -a`

Use case 2: Display information for a local package only

Code:

choco info package --local-only

Motivation: This use case allows users to retrieve information specifically for packages installed on their local machine. This can be useful for troubleshooting or managing the installed packages.

Explanation: The “–local-only” option limits the information displayed to only those packages that are installed locally. It ignores packages available from external sources.

Example output:

Chocolatey v0.10.15
chocolatey 0.10.15
 GÉANT S.A. <support@softwarecenter.co>
https://chocolatey.org/packages/../license-reconciliation
ChocolateyInstall.ps1 not found. The package will try to use one in its place.
Review the package URL above or in a browser at https://chocolatey.org/packages/chocolatey
To see the total community packages count, run `choco list -a`

Use case 3: Specify a custom source to receive packages information from

Code:

choco info package --source source_url|alias

Motivation: This use case allows users to retrieve package information from a specific source of their choosing. This can be useful when accessing packages from private sources or when using alternative package repositories.

Explanation: The “–source” option is used to specify a custom source URL or alias from which to retrieve package information. “package” should be replaced with the name of the package being queried, and “source_url|alias” should be replaced with the desired source URL or alias.

Example output:

Chocolatey v0.10.15
chocolatey 0.10.15
 GÉANT S.A. <support@softwarecenter.co>
https://chocolatey.org/packages/../license-reconciliation
ChocolateyInstall.ps1 not found. The package will try to use one in its place.
Review the package URL above or in a browser at https://chocolatey.org/packages/chocolatey
To see the total community packages count, run `choco list -a`

Use case 4: Provide a username and password for authentication

Code:

choco info package --user username --password password

Motivation: This use case allows users to provide authentication credentials when retrieving package information, which can be necessary when accessing private or secured sources.

Explanation: The “–user” and “–password” options are used to provide a username and password for authentication, respectively. “package” should be replaced with the name of the package being queried, and “username” and “password” should be replaced with the appropriate credentials.

Example output:

Chocolatey v0.10.15
chocolatey 0.10.15
 GÉANT S.A. <support@softwarecenter.co>
https://chocolatey.org/packages/../license-reconciliation
ChocolateyInstall.ps1 not found. The package will try to use one in its place.
Review the package URL above or in a browser at https://chocolatey.org/packages/chocolatey
To see the total community packages count, run `choco list -a`

Conclusion:

The “choco info” command in Chocolatey is a versatile tool for retrieving detailed information about packages. Whether users need specifics on a single package, want to limit the information to local packages, retrieve information from a custom source, or provide authentication credentials, this command has them covered. By utilizing the various options available, users can efficiently manage their package installations and troubleshoot any issues that arise.