From: Till Kamppeter <till.kamppeter@gmail.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: "Suffield, David" <david.suffield@hp.com>,
"'printing-summit@lists.linux-foundation.org'"
<printing-summit@lists.linux-foundation.org>,
Johannes Meixner <jsmeix@suse.de>,
Martin Pitt <martin.pitt@ubuntu.com>,
"printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Issue list from HP
Date: Wed, 15 Apr 2009 16:41:50 +0200 [thread overview]
Message-ID: <49E5F22E.7030404@gmail.com> (raw)
In-Reply-To: <49E5D2AB.7000000@redhat.com>
Tim Waugh wrote:
> Johannes Meixner wrote:
>> How is this implemented?
>> Via hardcoded stuff or is there a reliable working generic way?
>
> Via hardcoded stuff that Till wrote, which depends on all sorts of HPLIP
> internals, and which I will probably remove soon.
>
> Tim.
> */
>
It calls "hp-info -i -dURI". If the output contains "plugin = 1" the
plugin is needed. system-config-printer also checks for "plugin = 2" to
offer the plugin if it has optional enhancements. It uses the
"plugin-reason" to tell the user which enhancements the plugin supplies.
And it neverv creates a queue for a printer requiring the plugin if the
plugin is rejected by the user. So non-working queues are generally not
set up.
Till
next prev parent reply other threads:[~2009-04-15 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46089FAF7804194C8AD6458E272B07182174584144@GVW0676EXC.americas.hpqcorp.net>
2009-04-14 23:22 ` [Printing-architecture] Issue list from HP Till Kamppeter
[not found] ` <200904150120.n3F1Kg95023375@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <49E55C8C.2010500@apple.com>
[not found] ` <200904151139.n3FBdmZJ030596@dsl092-065-009.bos1.dsl.speakeasy.net>
2009-04-15 11:47 ` [Printing-architecture] [Printing-summit] " Till Kamppeter
[not found] ` <200904151206.n3FC6n7j030700@dsl092-065-009.bos1.dsl.speakeasy.net>
2009-04-15 14:28 ` Till Kamppeter
[not found] ` <alpine.LNX.2.00.0904151216120.10560@nelson.suse.de>
[not found] ` <49E5D2AB.7000000@redhat.com>
2009-04-15 14:41 ` Till Kamppeter [this message]
2009-04-27 16:16 ` [Printing-architecture] " 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=49E5F22E.7030404@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=david.suffield@hp.com \
--cc=jsmeix@suse.de \
--cc=martin.pitt@ubuntu.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-summit@lists.linux-foundation.org \
--cc=twaugh@redhat.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.