From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>,
Gutenprint Mailing List <gimp-print-devel@lists.sourceforge.net>
Subject: Re: [Printing-architecture] RFC: Patch for (libusb-based) USB backend for quirks files
Date: Thu, 18 Jul 2013 19:51:25 +0200 [thread overview]
Message-ID: <51E82B1D.7070007@gmail.com> (raw)
In-Reply-To: <D87733EE-8A2E-4F85-9978-715E38D8A22F@apple.com>
The patch is great. This makes it really much easier to handle quirk
rules for USB devices. This way one can ask users to add quirk rules
when they report a bug and so easily find the correct rules and the user
also has his problem properly solved until the rule makes it into CUPS.
Also the "whitelist" anti-quirk is a good idea to override
manufacturer-wide rules for some models.
What I would like to see is the possibility to have quirk rules (or at
least blacklisting) also for other backends. Also the prossibility to
prioritize backends via a directory of files would be great. This could
assure correct automated printer setup in all situations. In addition,
it must be assured that when one and the same printer is discovered by
various backends that these discoveries can be assigned to that one printer.
To conform with the files system hierarchy standard your patch needs a
small modification: Quirk files need to be searched in two directories,
once the one you are already using, /usr/share/cups/usb/, for the quirk
files of CUPS itself and of other packages, like Gutenprint, and second,
something in /etc/, like /etc/cups/backend/usb/, for rules defined by
the local user or admin.
Till
On 07/17/2013 06:02 PM, Michael Sweet wrote:
> All,
>
> Attached are patches for 1.7rc1 and 1.6.3 that add support for USB
> quirks files to the libusb-based USB backend. The purpose of these
> patches is to allow third-party drivers (Gutenprint, others) that
> provide their own backends to blacklist the USB printers they support,
> or for those drivers to identify the specific quirks those printers need
> to work with the standard USB backend.
>
> If there are no objections these will be part of the 1.6.4 update (last
> in that series) and part of the 1.7.0 release.
>
>
>
>
>
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture
>
next prev parent reply other threads:[~2013-07-18 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:02 [Printing-architecture] RFC: Patch for (libusb-based) USB backend for quirks files Michael Sweet
2013-07-18 17:51 ` Till Kamppeter [this message]
2013-07-18 19:05 ` Michael Sweet
2013-07-18 21:06 ` Till Kamppeter
2013-07-18 23:44 ` Michael Sweet
[not found] ` <20130801145448.GA10904@shaftnet.org>
2013-08-01 14:57 ` [Printing-architecture] [Gimp-print-devel] " Michael Sweet
[not found] ` <20130803011708.GA4773@shaftnet.org>
2013-08-05 14:48 ` 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=51E82B1D.7070007@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=gimp-print-devel@lists.sourceforge.net \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.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.