Filesets

There are conventions for fileset names which should be followed. A brief description of the conventions is included here, but for more information please see the HP Guidelines or the HP-UX Porting and Archive Centre Guidelines.

base-RUN	The run-time fileset for base. If base is entirely in the execution environment, the -RUN suffix may be omitted (just name the fileset base). If the product's execution environment mus tbe broken into smaller pieces for configurability, use -MIN and -AUX as follows.
base-MIN	The minimum runtime fileset for base
base-AUX	Auxiliary files for base other than those in base-MIN
base-SHLIBS	Shared library files for base
base-HELP	On-line help files.
base-KRN	Files need only to build a kernel. Can be removed after a kernel is built
base-PRG	Programming environment for base, exluding the files in base-KRN. If the header files base programming are small in size, include them in this fileset
base-INC	If the header files for base programming must be placed in a separate fileset, use base-INC
base-MAN	The manual entries associated with base. If the release notes for this product are small in size, include them in this fileset
base-DEMO	Files neede to run a demo for base
base-NOTES	The release notes for this product (if any). This fileset should only be defined if the release notes are fairly large, otherwise include the release notes in the base-MAN fileset

limit 80 characters. Type one_line_string

limit 2kB characters. limit 72 characters/line. Do not use <TAB> characters. Type multi_line_string

limit 8kB characters. limit 72 characters/line. Do not use <TAB> characters. Type multi_line_string

limit 1MB characters. limit 72 characters/line. Do not use <TAB> characters. Type multi_line_string

1. field by field, left to right
2. smaller "numbers" specify older revisions
3. ASCII comparison (0 number comparison (shorter numbers padded with trailing 0s), if the revision number contains only digits

Type software_specification

Type boolean

Type boolean

Type boolean

NOTE: Please specify all prerequisites as filesets. Do not depend on a subproduct, product, or bundle. There are some auxiliary tools that require all dependencies to be expressed as filesets.

Type software_specification

Shared library dependencies are a form of corequisite dependency. Mkpkg automatically detects these dependencies and includes them in the package. See shared_libraries for more information.

NOTE: Please specify all corequisites as filesets. Do not depend on a subproduct, product, or bundle. There are some auxiliary tools that require all dependencies to be expressed as filesets.

Type software_specification

Mkpkg Attributes

files

List of files to be installed by the fileset

links

List of files which are hard-linked. Each pair of files shows a link. This is useful for examining the fileset to see if hard links span directories and are likely to cause problems on remote machines with different physical file system partitioning.

symlinks

List of files which are symlinks along with their targets. This is useful for finding symlinks which are likely to break if the software is relocated by the user.

shared_libraries

List of shared libraries distributed as part of this fileset. This list is later utilized by mkpkgduring the automatic detection of shared library dependencies

shared_library

List of dependencies caused by executables linking with shared libraries in other filesets. This list is automatically generated by mkpkg.

Control Scripts