opkhp.blogg.se - Chocolatey package

Thus, the best way to determine the currently supported features is to create a test package, and look at the generated *.nuspec file: choco new testpackage Chocolatey includes additional optional functionality at the very top of the NuGet *.nuspec file. The *.nuspec file contains such basic information as the version, license, maintainer, and package dependencies. Therefore, the packages are based on the same principles, including that one stating that the package description (specification) must be stored in the XML format, known as Nuspec. The Chocolatey Windows package manager uses the same infrastructure as NuGet, that is the Visual Studio package manager. Install-ChocolateyPackage $packageName $fileType $silentArgs $url At the moment, chocolateyInstall.ps1 looks like the following: $packageName = 'windirstat Please note that the video features a bit outdated contents of the chocolateyInstall.ps1. I recommend you to take a look at the video showing the package creation.

chocolateyUninstall.ps1 for uninstalling your package.

The *.exe files in the package/downloaded to the package folder from chocolateyInstall.ps1 will have a link to the command line.

Any application files to include (it is highly recommended that you are the author in this case or you have the right to distribute files).

a package may contain an installation script.Ī Chocolatey package comprises of the following main elements:.

a package may contain embedded software.

read the What are Chocolatey Packages? section of the Chocolatey documentation.

Prerequisitesīefore getting started with the creation of a Chocolatey package, make sure you need to: In this article, we will take a brief look at the key stages of Chocolatey package creation.