Restrictions with the Use of RPM Packages

The following restrictions apply with the use of RPM packages:

Mixed dependency configurations are not supported, for example, if a PIF product depends on an RPM product, which depends on another PIF product.
RPM packages are accessed solely with the help of library.dct.
RPM autorequirements, for example, to shared libraries, shells, and so on, are not supported.
Disk space check (for complete transaction) is not available
Backup of RPM packages is not supported, so no rollback is available.
As appropriate RPM information is not provided, the progress of RPM package removal cannot be shown in the progress dialog.
Cancel of an RPM installation terminates after the particular RPM installation has been completed, to keep the RPM operation consistent.
You must not provide both types of packages, PIF and RPM, with the same product name in the same directory.