From: Michael Sweet <mike@easysw.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: printing-architecture@lists.freestandards.org,
Dan Kohn <dan@dankohn.com>, 'Ian Murdock' <imurdock@imurdock.com>,
lsb-discuss <lsb-discuss@lists.freestandards.org>
Subject: Re: [Printing-architecture] FHS extension and CUPS
Date: Fri, 19 Jan 2007 15:06:10 -0500 [thread overview]
Message-ID: <45B124B2.9080300@easysw.com> (raw)
In-Reply-To: <45B11475.4080704@gmail.com>
Till Kamppeter wrote:
> ...
> - Of CUPS 1.3 there is not even an alpha version, will it go final
> before the LSB 3.2 deadline?
Probably, but the more important issue is whether CUPS 1.3 will
be adopted by the distros before the LSB 3.2 deadline...
Right now I'm tied up with other (paying) tasks, but I'm hoping
to get 1.2.8 and 1.3b1 released in 3-4 weeks.
> - 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?
Given the scope of this "extension", I don't think it is necessary
(or fair) to force distros to ship CUPS 1.3 for LSB 3.2 compliance.
> 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.
The simplest solution is often the best solution. While we *will*
add support for configurable PPD paths to cups-driverd, using
symlinks now is the best way to go for CUPS 1.2.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
prev parent reply other threads:[~2007-01-19 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 18:56 [Printing-architecture] FHS extension and CUPS Till Kamppeter
2007-01-19 19:31 ` 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 [this message]
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=45B124B2.9080300@easysw.com \
--to=mike@easysw.com \
--cc=dan@dankohn.com \
--cc=imurdock@imurdock.com \
--cc=lsb-discuss@lists.freestandards.org \
--cc=printing-architecture@lists.freestandards.org \
--cc=till.kamppeter@gmail.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.