From: Michael Sweet <mike@easysw.com>
To: Christopher Yeoh <cyeoh@samba.org>
Cc: Andreas Jaeger <aj@suse.de>,
"Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
printing-architecture <printing-architecture@freestandards.org>,
Till Kamppeter <till.kamppeter@gmail.com>,
lsb-discuss <lsb-discuss@freestandards.org>,
Wendy Phillips <wendy.phillips@sun.com>
Subject: Re: [Printing-architecture] [lsb-discuss] Agreement on directory structure for printing
Date: Thu, 10 Aug 2006 19:06:17 -0700 [thread overview]
Message-ID: <44DBE619.4060706@easysw.com> (raw)
In-Reply-To: <17627.56745.848376.988255@localhost.localdomain>
Christopher Yeoh wrote:
> At 2006/8/10 18:43+0200 Andreas Jaeger writes:
>> 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
>> libraries
>>
>> Just don't hardcode lib but add a footnote that on lib64 systems,
>> lib64 is used,
>
> Yes, that would keep it consistent with the rest of the FHS.
Actually, I'd expect both 32-bit and 64-bit drivers to be supported
on a 64-bit system, and the default path we use in CUPS will include
both the 32-bit and 64-bit paths when CUPS is configured for multiple
architectures...
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
next prev parent reply other threads:[~2006-08-11 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1B47D24854C7BC4FA8DA28BEBB59B0BA463262@orsmsx419.amr.corp.intel.com>
2006-08-09 16:52 ` [Printing-architecture] [lsb-discuss] Agreement on directory structure for printing Till Kamppeter
[not found] ` <m3fyg4pmm8.fsf@gromit.moeb>
2006-08-11 1:30 ` Christopher Yeoh
2006-08-11 2:06 ` Michael Sweet [this message]
2006-08-14 17:10 ` Till Kamppeter
2006-08-17 15:56 ` Till Kamppeter
2006-08-17 17:45 McDonald, Ira
[not found] <3F62CBEE02D6404E98C65934617EB58268B93F@fmsmsx414.amr.corp.intel.com>
2006-08-14 17:30 ` Till Kamppeter
[not found] <1B47D24854C7BC4FA8DA28BEBB59B0BA4176AE@orsmsx419.amr.corp.intel.com>
2006-08-07 15:52 ` Till Kamppeter
2006-08-08 23:58 ` Wendy Phillips
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44DBE619.4060706@easysw.com \
--to=mike@easysw.com \
--cc=aj@suse.de \
--cc=cyeoh@samba.org \
--cc=lsb-discuss@freestandards.org \
--cc=printing-architecture@freestandards.org \
--cc=printing-sc@freestandards.org \
--cc=till.kamppeter@gmail.com \
--cc=wendy.phillips@sun.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.