svr4pkg - Manage Solaris SVR4 packages

Author:Boyd Adamson

Synopsis

Manages SVR4 packages on Solaris 10 and 11. These were the native packages on Solaris <= 10 and are available as a legacy feature in Solaris 11. Note that this is a very basic packaging system. It will not enforce dependencies on install or remove.

Options

parameter	required	default	choices	comments
name	yes			Package name, e.g. SUNWcsr
proxy	no			HTTP[s] proxy to be used if src is a URL.
response_file	no			Specifies the location of a response file to be used if package expects input on install. (added in Ansible 1.4)
src	no			Specifies the location to install the package from. Required when state=present.Can be any path acceptable to the pkgadd command's -d option. e.g.: somefile.pkg, /dir/with/pkgs, http:/server/mypkgs.pkg.If using a file or directory, they must already be accessible by the host. See the copy module for a way to get them there.
state	yes		present absent	Whether to install (present), or remove (absent) a package.If the package is to be installed, then src is required.The SVR4 package system doesn't provide an upgrade operation. You need to uninstall the old, then install the new package.

Examples

# Install a package from an already copied file
- svr4pkg: name=CSWcommon src=/tmp/cswpkgs.pkg state=present

# Install a package directly from an http site
- svr4pkg: name=CSWpkgutil src=http://get.opencsw.org/now state=present

# Install a package with a response file
- svr4pkg: name=CSWggrep src=/tmp/third-party.pkg response_file=/tmp/ggrep.response state=present

# Ensure that a package is not installed.
- svr4pkg: name=SUNWgnome-sound-recorder state=absent