All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Christopher Yeoh <cyeoh@samba.org>
Cc: "Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
	Michael Sweet <mike@easysw.com>,
	printing-architecture <printing-architecture@freestandards.org>,
	lsb-discuss <lsb-discuss@freestandards.org>,
	freestandards-fhs-discuss@lists.sourceforge.net,
	Wendy Phillips <wendy.phillips@sun.com>
Subject: Re: [Printing-architecture] [lsb-discuss] resend notes from lastweek
Date: Tue, 25 Jul 2006 19:26:42 +0200	[thread overview]
Message-ID: <44C65452.9040603@gmail.com> (raw)
In-Reply-To: <17606.15861.773455.901325@localhost.localdomain>

Christopher Yeoh wrote:
> 
> Yea, I agree /opt/vendor appears scattered, but symlinking them in
> through into /opt/lib/ and /opt/share/ should bring them all together
> without the need for adding a special printing directory to /opt. I'd
> like to avoid having a special case here unless it can be shown to be
> really necessary.
>

Would /opt/share/ppd/<supplier> and /opt/lib/printerdrivers/<supplier>
violate the FHS or can we define this as the standard places for
third-party files?

> Note that although 3rd party vendors will only have to install into
> one place, applications that look for them will still need to look in
> /usr/lib and /usr/local/lib in addition to /opt and at a higher level
> someone will need to work out precedence rules (say /usr/local ->
> /opt/ -> /usr in order of decreasing importance)

In a typical Linux distro with CUPS /usr/share/cups/model will contain
symlinks to /usr/share/ppd, /usr/local/share/ppd, and /opt/share/ppd and
so it will see all PPDs. The drivers are found by absolute paths in the
PPDs. Problem is how will CUPS handle priorities. If there are three
PPDs with equal NickNames but in different directories, the web
interface will show three equal list entries.

The priorities you suggested are good. /opt overrides /usr and so
manufacturer drivers (or updates downloaded as LSB packages from
linuxprinting.org) have priority against distro-included drivers. With
/usr/local having highest priority, drivers installed from source, for
example hacked by the admin will be preferrably used. So admins do not
need to wonder why their patches or CVS updates to not work due to the
distro's version of the driver still being installed.

> freestandards-fhs-discuss@lists.sourceforge.net is the best place for
> FHS discussions. Apologies if I hadn't responded to you before, but
> for some reason SourceForge unsubscribed me from the list and I didn't
> realise (I'm an FHS person). We go through periods of not much
> activity until there is enough in the queue to justify a new release.

Would the suggestion with /opt/share/ppd/<supplier> and
/opt/lib/printerdrivers/<supplier> for third-party drivers need a change
on FHS?

   Till


  parent reply	other threads:[~2006-07-25 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 15:25 [Printing-architecture] [lsb-discuss] resend notes from lastweek Fujinaka, Todd
     [not found] ` <17606.15861.773455.901325@localhost.localdomain>
2006-07-25 17:26   ` Till Kamppeter [this message]
2006-07-25 17:50   ` Till Kamppeter
     [not found] <3F62CBEE02D6404E98C65934617EB582441EF5@fmsmsx414.amr.corp.intel.com>
2006-07-25 13:06 ` Till Kamppeter

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=44C65452.9040603@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=cyeoh@samba.org \
    --cc=freestandards-fhs-discuss@lists.sourceforge.net \
    --cc=lsb-discuss@freestandards.org \
    --cc=mike@easysw.com \
    --cc=printing-architecture@freestandards.org \
    --cc=printing-sc@freestandards.org \
    --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.