Comment 31 for bug 1448092

Thank you very much, Steve.

> ... but lintian does not support analyzing such a package using the appropriate rules.

Then, Ubuntu community should not reject a package destined for /opt, based on lintian's analysis output until that tool is fixed to comply with all FHS specifications.

> Are there any technical blockers to placing the package's contents in
> /opt/ibm/pm, with symlinks to /etc/opt/ibm/pm and /var/opt/ibm/pm
> for the writable parts?

Yes, but only Ubuntu system (iso) is the blocker. Administrator (root) can NOT run (& man) commands in /opt/(s)bin (& /opt/man) without the path because /opt/(s)bin are not included in $PATH by default when they exist. This is another Ubuntu bug (in user profile initialization) for unconditional enforcement of the FHS standard while the system is actually not ready for.

Note: 1) As I tested, SuSE has supported /opt/(s)bin in $PATH if the directories exist, at least since sles10; Fedora/Red Hat/Ubuntu are not yet;
      2) "man" will work fine because it was designed in the configuration to look into /opt/man once /opt/(s)bin appear in $PATH.