A file containing package defaults for installing packages. This is currently only used on Solaris. The value will be validated according to system rules, which in the case of Solaris means that it should either be a fully qualified path or it should be in /var/sadm/install/admin.

Tells apt to allow cdrom sources in the sources.list file. Normally apt will bail if you try this.

A read-only parameter set by the package.

Whether configfiles should be kept or replaced. Most packages types do not support this parameter. Defaults to keep.

A read-only parameter set by the package.

What state the package should be in. On packaging systems that can retrieve new packages on their own, you can choose which package to retrieve by specifying a version number or latest as the ensure value. On packaging systems that manage configuration files separately from "normal" system files, you can uninstall config files by specifying purged as the ensure value. This defaults to installed.

OpenBSD supports 'flavors', which are further specifications for which type of package you want.

An array of additional options to pass when installing a package. These options are package-specific, and should be documented by the software vendor. One commonly implemented option is INSTALLDIR:

        packagex { 'mysql':
          ensure          => installed,
          source          => 'N:/packages/mysql-5.5.16-winx64.msi',
          install_options => [ '/S', { 'INSTALLDIR' => 'C:\mysql-5.5' } ],
        }

    Each option in the array can either be a string or a hash, where each
    key and value pair are interpreted in a provider specific way.  Each
    option will automatically be quoted when passed to the install command.

    On Windows, this is the **only** place in Puppet where backslash
    separators should be used.  Note that backslashes in double-quoted
    strings _must_ be double-escaped and backslashes in single-quoted
    strings _may_ be double-escaped.

A read-only parameter set by the package.

The package name. This is the name that the packaging system uses internally, which is sometimes (especially on Solaris) a name that is basically useless to humans. If you want to abstract package installation, then you can use aliases to provide a common name to packages:

      # In the 'openssl' class
      $ssl = $operatingsystem ? {
        solaris => SMCossl,
        default => openssl
      }

      # It is not an error to set an alias to the same value as the
      # object name.
      packagex { $ssl:
        ensure => installed,
        alias  => openssl
      }

      . etc. .

      $ssh = $operatingsystem ? {
        solaris => SMCossh,
        default => openssh
      }

      # Use the alias to specify a dependency, rather than
      # having another selector to figure it out again.
      packagex { $ssh:
        ensure  => installed,
        alias   => openssh,
        require => Packagex[openssl]
      }

A read-only parameter set by the package.

A file containing any necessary answers to questions asked by the package. This is currently used on Solaris and Debian. The value will be validated according to system rules, but it should generally be a fully qualified path.

A read-only parameter set by the package.

Where to find the actual package. This must be a local file (or on a network file system) or a URL that your specific packaging type understands; Puppet will not retrieve files for you, although you can manage packages as file resources.

A read-only parameter set by the package.

An array of additional options to pass when uninstalling a package. These options are package-specific, and should be documented by the software vendor. For example:

        packagex { 'VMware Tools':
          ensure            => absent,
          uninstall_options => [ { 'REMOVE' => 'Sync,VSS' } ],
        }

    Each option in the array can either be a string or a hash, where each
    key and value pair are interpreted in a provider specific way.  Each
    option will automatically be quoted when passed to the uninstall
    command.

    On Windows, this is the **only** place in Puppet where backslash
    separators should be used.  Note that backslashes in double-quoted
    strings _must_ be double-escaped and backslashes in single-quoted
    strings _may_ be double-escaped.

A read-only parameter set by the package.

This is an alias for package_settings. Currently we look for better (more generic) name for these options and our temporary choice is package_settings. Once the new name gets established, we'll deprecate build_options and switch to a new name. You must not use build_options and package_settings simultaneously.

    The definition of build options is provider specific. In general, these
    are certain properties which alter contents of a package being
    installed. An example of build options are the FreeBSD ports options.

    The build_options attribute is a property. This means that the options
    can be enforced during package installation and verified/retrieved
    for packages that are already installed.

    For example, portsx provider on FreeBSD implements the build options as
    port options (the ones you normally set with make config). There is a
    simple usage example for this particular type of build options (that is
    for portsx provider):

        packagex { 'www/apache22':
          build_options => { 'SUEXEC' => false }
        }

    The above manifest ensures, that apache22 is compiled without SUEXEC
    module.

    Despite the build_options are provider specific, the typical behavior,
    when you change package's build_options in your manifest, is to
    rebuild/reinstall package with new options.

Package settings. The definition of package settings is provider specific. In general, these are certain properties which alter contents of a package being installed. An example of package settings are the FreeBSD ports options.

    The package_settings attribute is a property. This means that the options
    can be enforced during package installation and verified/retrieved
    for packages that are already installed.

    For example, portsx provider on FreeBSD implements the package settings
    as port build options (the ones you normally set with make config).
    There is a simple usage example for this particular provider:

        packagex { 'www/apache22':
          package_settings => { 'SUEXEC' => false }
        }

    The above manifest ensures, that apache22 is compiled without SUEXEC
    module.

    Despite the package_settings are provider specific, the typical
    behavior, when you change package's package_settings in  your manifest,
    is to reinstall package with new settings.

The specific form of package management on FreeBSD. This is an extremely quirky packaging system, in that it freely mixes between ports and packages. Apparently all of the tools are written in Ruby, so there are plans to rewrite this support to directly use those libraries.

OpenBSD's form of pkg_add support.