[Printing-architecture] Automatic printer setup with Printer Applications
msweet at msweet.org
Thu Feb 25 13:33:41 UTC 2021
> On Feb 25, 2021, at 3:52 AM, Zdenek Dohnal <zdohnal at redhat.com> wrote:
> Sounds reasonable, except for crying in beer! That's never reasonable
> around here :D
> So udev-configure-printer would:
> 1) check if there is a USB device - if it is IPP-over-USB and isn't in
> allow list (probably there will be devices which will present themselves
> as IPP-over-USB, but it will be broken, so they want to fall back to
> printer application...), break out
Actually, I don't think you're going to find as many broken IPP-USB printers as you think since all but the first couple HP models implemented IPP-USB to get AirPrint certification, which means it got tested extensively... :)
> 2) find a printer application which supports the device
> 3) if it is not installed, install it - this will need to be updated -
> currently PackageKit is used in scp lib, but PackageKit is going away in
> the future  - I heard there is some work in DNF regarding PackageKit
> functionality, but I'm not sure how far they are. Not mentioning it is a
> distro specific package manager, not sure if other distros have already
> some alternative to PackageKit.
Up to you, but I would expect some user confirmation before installing any software on my computer...
> 4) auto-add the device to a printer application - scp lib for adding
> print queues is now for CUPS only and written in Python, so it will need
> to be rewritten in C/Go using PAPPL.
Why? The printer application can just be run with the "autoadd" sub-command, no need to link against PAPPL for that.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 874 bytes
Desc: Message signed with OpenPGP
More information about the Printing-architecture