System Configuration

Overview
Configuration
Defaults

Overview

There are many attributes and defaults which are shared across all packages developed on a single machine. These defaults cover a wide range of system-specific items, such as the list of log files that are modified by daemons and should be ignored during manifest generation.

Configuration

spurious names: List of files which are frequently modified by normal system activity and should be ignored by mkpkg when looking for newly installed files. Please see the description of the Create file manifest action for more information
search directories: List of directories to search for newly installed files. Please see the description of the Create file manifest action for more information
http server: The fully-qualified ip-name of the web server.
This attribute is only used when mkpkg is used to build a web-based software library.
http directory: The pathname of the root of the web document hierarchy
This attribute is only used when mkpkg is used to build a web-based software library.
html directory: The path from the web document root to the root of the software library.
This attribute is only used when mkpkg is used to build a web-based software library.
system categories: This attribute is only used by the HP-UX Public Domain Software Archive. It contains a list of the system categories and their titles.
reference depot: If this attribute is set, mkpkg will search this depot for shared libraries (see the action Search for system shared libraries) and bundle contents for associated bundles.
swpackage depot: If this attribute is set, mkpkg will package the software into this central depot instead of building a compressed tar depot for the package. The attribute should be a depot descriptor.

Defaults

architecture

The target system for which this bundle is intended. Summarizes the supported hardware and operating systems.

There are three parts of the architecture attribute: OS, OS revision, and machine type. The attribute is structured like:

The OS is always "HP-UX".

The OS revision is different for ISU and Core software. For Core software (BSU's and CSU's) the OS revision is identical to the revision attribute, so the architecture attribute changes for each HP-UX release. For ISU software the OS revision is the minimum OS revision necessary to run the software. For example, if the software runs on 10.00 and 10.10, then you would specify B.10.00.

The machine type can only have three values:

700 runs on series 700 only

800 runs on series 800 only

700/800 runs on either series 700 or series 800

machine_type

machine types on which the bundle will run (uname -m). May use shell pattern matching to cover a range of machine types. Some examples:

`9000/7??`	series 700 only
`9000/[68]??`	series 800 only
`9000/[678]??`	series 700 and series 800

os_name

OS'es on which the bundle will run (uname -s)

HP-UX

os_release

OS releases on which the bundle will run (uname -r). May use shell pattern matching to cover a range of releases. Some examples:

`?.10.*`	any 10.0 release
`?.10.\|?.11.`	any 10.0 or 11.0 release

os_version

OS versions on which the product will run. May use shell pattern matching to cover a range of releases.

`*`	Allow all versions

directory

The default, absolute pathname of the direcotry which is the root of the file system tree under which the product will be installed. Can be re-mapped by the user if is_locatable is TRUE.

For information on configuring software please see the Software Porting and Configuration Guide (for non-HP software), or the HP Guidelines (for HP software)

is_locatable

A boolean, which if set to TRUE, allows users to install the product into an alternate product directory.

static compile flags

dynamic compile flags

`700`	runs on series 700 only
`800`	runs on series 800 only
`700/800`	runs on either series 700 or series 800