From: Ian Murdock <imurdock@imurdock.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
Michael Sweet <mike@easysw.com>,
lsb-discuss <lsb-discuss@freestandards.org>,
printing-architecture <printing-architecture@freestandards.org>,
Wendy Phillips <wendy.phillips@sun.com>
Subject: Re: [Printing-architecture] resend notes from last week
Date: Tue, 25 Jul 2006 07:29:24 -0400 [thread overview]
Message-ID: <44C60094.3030809@imurdock.com> (raw)
In-Reply-To: <44C5FE6D.3010803@gmail.com>
Till Kamppeter wrote:
> Michael Sweet wrote:
>> Till Kamppeter wrote:
>>> Are more directories needed?
>>
>> /usr/local/share/ppd/<supplier>/<manufacturer>
>> /usr/local/lib/printdrivers/<supplier>
>>
>
> Is it not enough agreeing on one ofthe pairs
>
> /usr/local/share/ppd/<supplier>/<manufacturer>
> /usr/local/lib/printdrivers/<supplier>
>
> and
>
> /opt/printing/ppd/<supplier>/<manufacturer>/
> /opt/printing/drivers/<supplier>/
>
> Why are both pairs needed?
/usr/local is where system administrators can install printer drivers
(say, downloaded manually from linuxprinting.org), and /opt is where
vendors can install printer drivers (say, installed via an LSB package
downloaded from the vendor's website) that aren't shipped as part of
the operating system. Question: Is /opt/printing consistent with the
FHS? Wouldn't it be /opt/<vendor>? Yes, that means there's no
canonical place for vendors to drop printer drivers so they
are available system-wide, but that's the equivalent problem of
not having a single path element for third-party
executables, and should presumably be solved in the same manner.
(Adding lsb-discuss to this discussion, so we can get FHS feedback.)
--
Ian Murdock
317-863-2590
http://ianmurdock.com/
"Don't look back--something might be gaining on you." --Satchel Paige
next prev parent reply other threads:[~2006-07-25 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 23:16 [Printing-architecture] resend notes from last week Fujinaka, Todd
2006-07-25 8:58 ` Till Kamppeter
2006-07-25 11:09 ` Michael Sweet
2006-07-25 11:20 ` Till Kamppeter
2006-07-25 11:29 ` Ian Murdock [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 15:04 Fujinaka, Todd
2006-07-24 16:19 Fujinaka, Todd
2006-07-24 21:38 ` Till Kamppeter
2006-07-20 19:25 Wendy Phillips
2006-07-20 19:46 ` Till Kamppeter
2006-07-20 20:43 ` Michael Sweet
2006-07-24 13:14 ` Till Kamppeter
2006-07-24 14:54 ` Michael Sweet
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=44C60094.3030809@imurdock.com \
--to=imurdock@imurdock.com \
--cc=lsb-discuss@freestandards.org \
--cc=mike@easysw.com \
--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.