mksear generates a UWIN self-extracting installation archive. File operands matching *
.files are files
containing a list of
$INSTALLROOT relative files, one per line, to be copied to the output archive. File
entries matching *
.files are scanned recursivley. Implicit for the
base sear:
posix.dll,
ast54.dll
,
shell11.dll,
cmd12.dll,
ksh.
Each file entry is a / relative path of a file to be packaged. Symlinks only include the symlink, not the link target.
Directories name themselves and recursively all contents. In general omitting directories and spelling out each file
is preferable. Entries of the form to:op:[from] are controlled by the operation op when
the sear is read. The operations are:
- to::from
Map the local system physical path from to the
package path to.
- to::
- Delete to on the system that unpackages the sear if it exists.
- to:GENERATE:script
The shell script is executed
with standard output redirected to to.
- to:MAP:[from]
Generate a map/basename(to)/current
archive for stack trace debugging, where from optionally specifies the source component directory where to
is built.
- to:PRESERVE:
to is added to the
stdinstall(1) db with the --preserve attribute when
the sear is created. to.new is created when the sear is read. After all files are read
stdinstall(1) is called to determine if to.new
or to prevails for all to.new.
- to:RETAIN:
to is added to the
stdinstall(1) db with the --retain attribute when the
sear is created. to.new is created when the sear is read. After all files are read
stdinstall(1) is called to determine if to.new
or to prevails for all to.new.
File operands matching *
.finish are scripts that will be run after all archive files have been extracted. Other
file operands are simply copied to the output archive.
Local system files are viewpathed relative to $INSTALLROOT with / used as a last resort. EXCEPTION: the UWIN
posix headers are typically packaged from /usr/include rather than a viewpathed build directory.