On Wed 11 Aug 2021 at 14:15:49 +0200, Erwan David wrote: > Le 11/08/2021 à 12:36, Brian a écrit : > > On Wed 11 Aug 2021 at 08:19:37 +0100, Brad Rogers wrote: > > > > > On Tue, 10 Aug 2021 19:54:23 +0100 > > > Brian <a...@cityscape.co.uk> wrote: > > > > > > Hello Brian, > > > > > > > As I've said previously, a future CUPS will not support printer drivers. > > > > HPLIP provides printer drivers. There will be little point in Debian > > > > packaging HPLIP, wouldn't you agree? But this is a few years away. > > > > > > When, eventually, all HP printers run driverless _and_ no no-driverless > > > printer exist 'in the wild', yes. Until then, I'd expect HPLIP to > > > remain. Debian is, after all, about choice. > > > > The condition you lay down in the first sentence is not a factor in > > determining whether Debian packages HPLIP. HPLIP uses PPDs and drivers; > > a future CUPS will not work with PPDs and drivers. The choice will be > > to have a working printing system using driverless or a non-working > > printing system. > > > > Or to have a non working printing solution because the new one does not > cover the full range pof printing setups. Autodiscovery is good when > possible, but removing any possibility not to use it is a fault, when > autodiscovery does not work. I hope before cups is made unable to use PPD, > the driverless system is made able to be given remote printers adresses and > capabilities (also thinking to old printers which do not advertise > capabilities the way you want).
Regarding autodiscovery not being a suitable technique: perhaps the final item on page 22 at https://ftp.pwg.org/pub/pwg/liaison/openprinting/presentations/cups-plenary-may-2021.pdf will help. The point of "profiles" is to provide a simple way for enterprises to configure/deploy IPP Everywhere queues (pointed at real printers, a central CUPS server, etc.) when mDNS/DNS-SD isn't feasible. -- Brian