[cups] Using the new IPP Everywhere PPD generator with cups-browsed

[Michael Sweet]

cupsGetServerPPD has no parameter to specify the URI of the printer, which is necessary to generate the PPD.  Conceptually we might be able to support IPP/IPPS URIs ("ipp://ip-or-hostname/..." and "ipps://ip-or-hostname") however there is also the issue of support files (icons, message catalogs, etc.) that have yet to be addressed.


> On Feb 12, 2015, at 10:34 PM, Till Kamppeter <till.kamppeter at gmail.com> wrote:
> 
> My suggestion is to let CUPS functions like "cupsGetServerPPD()" support the model string "everywhere" to get a PPD from the PPD generator back. Then clients can access the new functionality without API change.
> 
>   Till
> 
> On 13.02.2015 01:14, Till Kamppeter wrote:
>> Hi,
>> 
>> I am testing the new PPD generator for IPP Everywhere printers from
>> 
>> https://www.cups.org/str.php?L4258
>> 
>> by having backported the patches to CUPS 2.0.2. I have no problem to
>> create a queue with the lpadmin command with "-m everywhere" only with a
>> small quirk:
>> 
>> https://www.cups.org/str.php?L4579
>> 
>> Already for some time cups-browsed (from cups-filters) is capable of
>> discovering IPP Everywhere printers and auto-creating queues for them
>> (with "CreateIPPPrinterQueues Yes" in /etc/cups/cups-browsed.conf) but
>> these queues are set up with System V interface scripts due to lack of a
>> PPD generator.
>> 
>> Now I want to use the new generator provided by CUPS, but have no idea
>> yet how to do this. cups-browsed speaks IPP to CUPS to create queues.
>> How should I proceed.
>> 
>> Naturally I will do a fallback to the interface scripts on failure, so
>> that cups-browsed keeps working with older CUPS versions.
>> 
>> Thanks in advance for any help.
>> 
>>    Till
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair