# Chocolatey has a custom PowerShell host that will time these calls # Read-Host, PromptForChoice, etc are not blocking calls with Chocolatey. # command line call: `choco install -params "'/LICENSE:value'"` Here's an example of what we can achieve. Let's customize a package with a call similar to `choco install -params "'/LICENSE:value'"``. 📝 NOTE Get-PackageParameters is available now with a dependency on chocolatey-core.extension, and in a future version of Chocolatey (see #312), it will also be one of Chocolatey's built-in functions. If you are hosting your own internal feeds, it is recommended you follow this behavior, but not required. This is especially true of the packages on the community feed. A package installation should require no arguments and the default values should just happen. 📝 NOTE Package parameters are not meant to be a substitute for sensible default values. This is more of a way for a package consumer to override the default silent arguments that are passed to the native installer. 📝 NOTE There is also the concept of "Install Arguments", or silent arguments you can pass through transparently to the native installer. DEPRECATED - Step 3 (alternative) - Parse Your Own.It does offer a nice way of providing that information for folks. You can use package parameters to set up arguments to the native installer, but that is typically done from the consumer end with Install Arguments. Package parameters provide a way for a package consumer to make choices about how they want things installed and configuration of the underlying software. Each one of these arguments is detailed here. When installing a Chocolatey Package, it is possible to use a number of arguments to control how the package is installed.
0 kommentar(er)
