From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Fujinaka, Todd" <todd.fujinaka@intel.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: Mon, 24 Jul 2006 23:38:39 +0200 [thread overview]
Message-ID: <44C53DDF.6090201@gmail.com> (raw)
In-Reply-To: <D90275D3D462F94E9B3892626804E08C01580B06@orsmsx412.amr.corp.intel.com>
Fujinaka, Todd wrote:
>>-----Original Message-----
>>From: printing-architecture-bounces@lists.freestandards.org
>>[mailto:printing-architecture-bounces@lists.freestandards.org] On
>
> Behalf Of
>
>>Michael Sweet
>>
>>Till Kamppeter wrote:
>>
>>>...
>>>Does this mean that putting a third-party CUPS filter into
>>>/usr/lib/cups/filter/ is no violation of FHS?
>>
>>Technically yes, since they aren't part of the standard printing
>>system. That said, there is a long history of putting drivers
>>(or interface scripts, or filters, etc.) in /usr/share, so it
>>might make sense to add a grandfather clause for this, or make
>>it one of several possible directories - OS vendors put them in
>>/usr/share, other vendors in /opt/printing/share, local drivers
>>in /usr/local/share, etc.
>
>
> It is my understanding that /usr/share shouldn't change. I think Till is
> forgetting that CUPS is included by the distro, so having things in
> /usr/share/CUPS at install time is not a problem.
>
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.
>
>>>Would then putting a driver and its PPD into the directories
>>>
>>>/usr/share/ppd/<supplier>/<manufacturer>/
>>>
>>>and
>>>
>>>/usr/lib/printdrivers/<supplier>
>>>
>>>because these directories are a core part of the OS?
>>>
>>>Or do we still need the alternative location /opt/printing/?
>>
>>I'd say to support both - /usr for OS-supplied stuff, /opt and
>>/usr/local for locally-installed stuff.
>
>
> It is my understanding nothing should be installed into /usr while the
> system is running normally. There are times when packages are updated,
> but I think the assumption is that updates are not happening during
> "normal use." Also, /usr is the domain of the distro and I doubt they
> want you to touch it without their OK.
>
So third-party CUPS drivers are violating the standards currently, due
to requirements of CUPS.
Till
next prev parent reply other threads:[~2006-07-24 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 16:19 [Printing-architecture] resend notes from last week Fujinaka, Todd
2006-07-24 21:38 ` Till Kamppeter [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 15:04 Fujinaka, Todd
2006-07-24 23:16 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
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=44C53DDF.6090201@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@freestandards.org \
--cc=printing-sc@freestandards.org \
--cc=todd.fujinaka@intel.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.