Defining collectively relocatable objects

Follow these steps to define package objects as collectively relocatable:

1. Define a value for the BASEDIR parameter.

   Put a definition for the BASEDIR parameter in your pkginfo(F) file. 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.

2. Define objects as collectively relocatable in the prototype(F) file.

   An object is defined as collectively relocatable by using a relative pathname in its entry in the prototype file. A relative pathname does not begin with a slash. For example, src/myfile is a relative pathname, while /src/myfile is a fixed pathname.

   ---

   NOTE: A package can deliver some objects with relocatable locations and others with fixed locations.

   ---

• if the admin file contains basedir=ask and pkgadd(ADM) was not invoked in non-interactive mode, then the installer's response to pkgadd(ADM) when asked where relocatable objects should be installed (this overrides the value for BASEDIR in the package's pkginfo(F) file, if any)

• the value of BASEDIR as it is defined in the admin file used during the pkgadd(ADM) process (the BASEDIR value assigned in the admin file overrides the value of the pkginfo(F) file)

• the value of BASEDIR as it is defined in your pkginfo(F) file (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 pkginfo(F) file, then BASEDIR defaults to /