How to use the command choco new (with examples)

The choco new command is used to generate new package specification files with Chocolatey. It is a helpful command for creating new Chocolatey packages and customizing them according to specific requirements.

Use case 1: Create a new package skeleton

Code:

choco new package

Motivation: This use case is useful when you want to quickly generate a basic package skeleton. It creates a package with the default settings, allowing you to further customize it.

Explanation:

• package: This is the name of the package. Replace it with the desired package name.

Example output:

Creating the specification for the new package 'package'...
package.nuspec has been created.
packageInstall.ps1 has been created.
packageUninstall.ps1 has been created.
package.nuspec has been updated with dependency and/or framework information.

Use case 2: Create a new package with a specific version

Code:

choco new package --version version

Motivation: This use case is helpful when you want to create a package with a specific version. It allows you to specify the desired version during package creation.

Explanation:

• package: This is the name of the package. Replace it with the desired package name.
• version: This is the specific version of the package that you want to create. Replace it with the desired version number.

Example output:

Creating the specification for the new package 'package'...
package.nuspec has been created with version 'version'.
packageInstall.ps1 has been created.
packageUninstall.ps1 has been created.
package.nuspec has been updated with dependency and/or framework information.

Use case 3: Create a new package with a specific maintainer name

Code:

choco new package --maintainer maintainer_name

Motivation: This use case comes in handy when you want to assign a specific maintainer name to the package. It allows you to set the package’s maintainer during its creation.

Explanation:

• package: This is the name of the package. Replace it with the desired package name.
• maintainer_name: This is the name of the maintainer you want to assign to the package. Replace it with the desired maintainer name.

Example output:

Creating the specification for the new package 'package'...
package.nuspec has been created with maintainer 'maintainer_name'.
packageInstall.ps1 has been created.
packageUninstall.ps1 has been created.
package.nuspec has been updated with dependency and/or framework information.

Use case 4: Create a new package in a custom output directory

Code:

choco new package --output-directory path/to/directory

Motivation: This use case is useful when you want to create the package files in a specific output directory. It allows you to specify a custom directory where all the package files will be generated.

Explanation:

• package: This is the name of the package. Replace it with the desired package name.
• path/to/directory: This is the path to the custom output directory where you want to generate the package files. Replace it with the desired directory path.

Example output:

Creating the specification for the new package 'package'...
package.nuspec has been created.
packageInstall.ps1 has been created.
packageUninstall.ps1 has been created.
package.nuspec has been updated with dependency and/or framework information.
Files have been generated in the custom output directory 'path/to/directory'.

Use case 5: Create a new package with specific 32-bit and 64-bit installer URLs

Code:

choco new package url="url" url64="url"

Motivation: This use case is helpful when you want to specify 32-bit and 64-bit installer URLs for the package. It allows you to define separate URLs for different architectures.

Explanation:

• package: This is the name of the package. Replace it with the desired package name.
• url: This is the URL of the 32-bit installer for the package. Replace it with the desired URL.
• url64: This is the URL of the 64-bit installer for the package. Replace it with the desired URL.

Example output:

Creating the specification for the new package 'package'...
package.nuspec has been created.
packageInstall.ps1 has been created.
packageUninstall.ps1 has been created.
package.nuspec has been updated with dependency and/or framework information.
32-bit installer URL set as 'url'.
64-bit installer URL set as 'url64'.

Conclusion:

The choco new command is a versatile tool for generating new package specification files with Chocolatey. By using different arguments, you can fully customize the package during its creation, allowing you to create packages tailored to your specific needs.