From: Michael Sweet <mike@easysw.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Wendy Phillips <wendy.phillips@sun.com>,
printing-architecture <printing-architecture@freestandards.org>,
"Printing-Sc (E-mail)" <printing-sc@freestandards.org>
Subject: Re: [Printing-architecture] resend notes from last week
Date: Tue, 25 Jul 2006 07:09:34 -0400 [thread overview]
Message-ID: <44C5FBEE.5070901@easysw.com> (raw)
In-Reply-To: <44C5DD23.1030400@gmail.com>
Till Kamppeter wrote:
> Fujinaka, Todd wrote:
>>> -----Original Message-----
>>> From: Till Kamppeter [mailto:till.kamppeter@gmail.com]
>>>
>>> But third-party CUPS drivers go into /usr/lib/cupss/filter and
>>> /usr/share/cups/model. So there is third-party software which goes into
>>> /usr.
>>
>> Yes, this is wrong, AFAIK. CUPS can have 3rd party drivers /usr (in
>> specific places) as long as the distro provides them. Other people (like
>> printer manufacturers) are not allowed to add to /usr.
>>
>>
>>> So third-party CUPS drivers are violating the standards currently, due
>>> to requirements of CUPS.
>>
>> Yes. Currently this is what CUPS does. Mike Sweet said he'd change
>> things around to allow other directories (correct me if I'm wrong).
>>
>> I keep harping on the FHS because it's a requirement of LSB, and I'm
>> working on the LSB project. We'd like to have the printing directory
>> structure in LSB, but if the printing directory structure conflicts with
>> the FHS we'd have ambiguities. Ambiguous standard won't be much use to
>> anyone.
>>
>
> Then I would suggest that we settle on
>
> /usr/share/ppd/<supplier>/<manufacturer>/
>
> dor the PPDs which make part of the distribution and
>
> /usr/lib/printdrivers/<supplier>
>
> for the drivers which make part of the distribution.
>
> The third-party PPDs go into
>
> /opt/printing/ppd/<supplier>/<manufacturer>/
>
> and the third-party drivers into
>
> /opt/printing/drivers/<supplier>/
>
> Are more directories needed?
/usr/local/share/ppd/<supplier>/<manufacturer>
/usr/local/lib/printdrivers/<supplier>
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Publishing Software http://www.easysw.com
next prev parent reply other threads:[~2006-07-25 11:09 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 [this message]
2006-07-25 11:20 ` Till Kamppeter
2006-07-25 11:29 ` Ian Murdock
-- 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=44C5FBEE.5070901@easysw.com \
--to=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.