Typically, a component of a PIF product can be installed in all UNIX and Linux operating environments. If you want a component to be installed only on a specific operating environment, you define the component as platform-specific. You specify the desired operating environment through the #sys: keyword in the prototype file. The component is installed only on that target computer whose operating environment matches the specified platform identification (PlatformID parameter). If no platform-specific component is found during installation, the default component with the PlatformID = Any is installed on the target computer.
A suitable example for the use of platform-specific components is the installation of a shared library. Shared library names differ in different UNIX operating environments. On Sun Solaris and Linux systems, the names of shared libraries end with .so; on HP-UX, they end with .sl; and on IBM-AIX, they end with .o or .a. To cover these different naming conventions, for example, for HP-UX and Solaris systems in your network, add two platform-specific components to your PIF product. The first component stores the HP-UX library with the extension .sl, and the second component stores the Solaris library with the extension .so.
The Packager distinguishes between products that can be installed on any UNIX and Linux operating environment (PlatformID = Any) and products for a specified operating environment. If a product can be installed on any operating environment, all platform-specific components are added to the PIF product. If the product can be installed only on a specified operating environment, all components that do not match the PlatformID parameter are removed from the PIF product.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|