Defining collectively relocatable objects
Follow these steps
to define package objects as collectively relocatable:
All objects defined as collectively relocatable are put under the same
root directory on the installation machine.
The root directory value will be one of the following (and in
Define a value for the BASEDIR parameter.
Put a definition for the BASEDIR parameter in your
This parameter names a directory where
relocatable objects will be placed by default.
If you supply no value for BASEDIR,
no package objects are considered as collectively relocatable.
Define objects as collectively relocatable in the
An object is defined as collectively relocatable by using a relative
pathname in its entry in the
A relative pathname does not begin with a slash.
For example, src/myfile
is a relative pathname, while /src/myfile is a fixed pathname.
A package can deliver some objects with relocatable locations and
others with fixed locations.
if the admin file contains basedir=ask and
was not invoked in non-interactive mode, then the installer's response
when asked where relocatable objects should be
installed (this overrides the value for BASEDIR in the package's
file, if any)
the value of BASEDIR as it is defined in the admin
file used during the
(the BASEDIR value assigned in the admin file overrides
the value of the
the value of BASEDIR as it is defined in your
(this value is used only as a default in case the other two
possibilities have not supplied a value)
if the admin file contains basedir=default and no BASEDIR
is set in the package's
file, then BASEDIR
defaults to /
Defining individually relocatable objects
4. Making package objects relocatable
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003