[lsb-discuss] [Printing-architecture] Agreement on directory structure for printing

Andreas Jaeger aj at suse.de
Thu Aug 10 09:43:43 PDT 2006

Till Kamppeter <till.kamppeter at gmail.com> writes:

> Bastian, Waldo wrote:
>> The admin paths in section 5 still needs adjustment.
> Below is the version with everything corrected.
> What about 64-bit systems (x86-64, ppc64, and s390x) which have a
> /usr/lib64/ directory for dynamic/shared libraries?
> We could go with
> {/usr,/usr/local,/opt}/lib/printdriver

> only if the drivers do not ship any shared libraries which provide
> functionality for other drivers. If a supplier wants to ship a library
> for both 32- and 64-bit only for its own use, he has the total liberty
> of directory structure under ../printdriver/<supplier>/ and could
> theoretically have lib/ and lib64/ directories there.

But then everybody does as they like and you get confusion - and you
will not be able to support both 32-bit and 64-bit printing software
at the same time (this might not happen in most case but anyway)

On x86-64, ppc64 and s390x I suggest:
{/usr,/usr/local,/opt}/lib/printdriver for 32-bit x86, ppc, s390 libraries
{/usr,/usr/local,/opt}/lib64/printdriver for 64-bit x86-64, ppc64,s390x

Just don't hardcode lib but add a footnote that on lib64 systems,
lib64 is used,

> [...]

 Andreas Jaeger, aj at suse.de, http://www.suse.de/~aj/
  SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.linux-foundation.org/pipermail/lsb-discuss/attachments/20060810/8968b665/attachment.pgp 

More information about the lsb-discuss mailing list