All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Dan Kohn <dan@dankohn.com>, 'Ian Murdock' <imurdock@imurdock.com>
Cc: printing-architecture@lists.freestandards.org,
	lsb-discuss <lsb-discuss@lists.freestandards.org>
Subject: [Printing-architecture] FHS extension and CUPS
Date: Fri, 19 Jan 2007 18:56:53 +0000	[thread overview]
Message-ID: <45B11475.4080704@gmail.com> (raw)

Hi,

I have posted a feature request for CUPS being adapted to the new FHS 
extension 
(http://lists.freestandards.org/pipermail/printing-architecture/2006/001512.html) 
for printing:

http://www.cups.org/str.php?L2202

Mike has answered that he will implement this in CUPS 1.3.

The problems are

- Of CUPS 1.3 there is not even an alpha version, will it go final
   before the LSB 3.2 deadline?

- Novell and Red Hat want to put out an update to fulfill the FHS
   extensions. Is it not perhaps a too high impact for an enterprise
   distro to replace CUPS 1.2 (x >> 0) by CUPS 1.3, especially 1.3.0?

Or should we better recommend to the distros to simply do

ln -s /usr/share/ppd /usr/share/cups/model/usrshareppd
ln -s /opt/share/ppd /usr/share/cups/model/optshareppd
ln -s /usr/local/share/ppd /usr/share/cups/model/usrlocalshareppd

in their CUPS package for now? This makes CUPS searching for the PPDs in 
the right places.

    Till


             reply	other threads:[~2007-01-19 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 18:56 Till Kamppeter [this message]
2007-01-19 19:31 ` [Printing-architecture] FHS extension and CUPS Ian Murdock
2007-01-19 19:52   ` Till Kamppeter
2007-01-19 20:26   ` Michael Sweet
2007-01-23 17:54     ` Till Kamppeter
2007-01-19 20:06 ` 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=45B11475.4080704@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=dan@dankohn.com \
    --cc=imurdock@imurdock.com \
    --cc=lsb-discuss@lists.freestandards.org \
    --cc=printing-architecture@lists.freestandards.org \
    /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.