If the dependency is already met, nothing happens, and your LOB application is installed. By defining the specific jre package id and version this LOB application requires, you need only worry about issuing a choco install LOB -y command on your target system, and Chocolatey will first check if the dependency is installed, and whether it needs to be upgraded based on the version of the dependency defined. For example, you may have a LOB application packaged with Chocolatey that takes a dependency on a particular version of Java Runtime Environment. When a package has a dependency defined, Chocolatey ensures that that dependency is first installed before installing the requested package. Understanding how Dependencies are installed For more information on the available version ranges and their syntax please see the NuGet SemVer Reference documentation available from .Īdditionally, any time you run the choco new command to manually build a new Chocolatey Package, the included nuspec template will include information about dependencies and how to use them in the Dependencies section of the file. Version SemanticsĬhocolatey follows the NuGet SemVer notation, including exact versions, minimum inclusive, maximum exclusive etc etc. In our particular example above the chocolatey-core.extension package will resolve at least the 1.3.3 version of the package, unless a newer version is available on your configured source(s). If you do NOT provide a version number, Chocolatey will attempt to resolve the dependency to the latest stable release available on the available source(s) per your Chocolatey configuration, or command line you passed.
You will notice in the above sample that there are two elements to a : This file contains all of the metadata about a particular Chocolatey package including:Ī nuspec also includes a section for defining package dependencies.Ī common example that you'll see across many Chocolatey packages on the Community Repository looks like the following: Understanding Dependency Syntaxĭependencies for a particular application are all defined within a package's nuspec file. This allows you to simplify complex application requirements into a single easy-to-use Chocolatey package. Chocolatey being built on top of a NuGet framework means that we can take advantage of the rich dependency experience that NuGet provides to developers.
0 kommentar(er)
