HPLIP installer does not care where CUPS is actually installed

[Johannes Meixner]

See
https://bugzilla.novell.com/show_bug.cgi?id=676897
--------------------------------------------------------------------
a problem when installing HP Linux Imaging and Printing
from hplipopensource.com
...
The package from hplipopensource.com
puts the files in ... /usr/lib64/
...
This causes a problem because the version
of CUPS in the openSuSE distribution expects
them in /usr/lib/ and when they can't be found,
you guessed it, you can't print.
--------------------------------------------------------------------

See "Compliance with Upstream CUPS" at
http://en.opensuse.org/Portal:Printing
--------------------------------------------------------------------
openSUSE 11.3 provides a major cleanup of CUPS.
...
The main change is that the "/usr/lib/cups/" directory
is used on all platforms (in particular no longer
"/usr/lib64/cups" on the 64-bit x86_64 platform).
For background information see
https://bugzilla.novell.com/show_bug.cgi?id=575544#c2
which reads in particular:

Upstream CUPS installs executables
(in particular backends and filters)
into /usr/lib/ in any case which is
the right place. Compare /usr/bin/
there is nothing like /usr/bin64/ because
for executables special ...64 directories
do not make sense.
In contrast libraries like libcups.so
and libcupsimage.so must be installed
into /usr/lib/ and /usr/lib64/
--------------------------------------------------------------------

In general:

Third party software for CUPS
(e.g. HPLIP from hplipopensource.com)
should not blindly install its files
into whatever hardcoded directory.

Instead the third-party software installer
should run cups-config to query CUPS
about its actual directories, e.g.
  cups-config --serverbin

Think about a 32-bit CUPS installation
on a x86_64 system or a self-compiled
CUPS from upstream on a x86_64 system.

Only if the cups-config query fails,
the third-party software installer
should use a reasonable hardcoded
directory as fallback.