Re: Recommended way to manually add an undiscovered IPP printer in CUPS 3.x

On 8/1/26 22:41, Michael Sweet wrote:
> Till,
> 
>> On Aug 1, 2026, at 3:50 PM, Till Kamppeter <[email protected]> wrote:
>> ...
>> But how to proceed under CUPS 3.x?
> 
> CUPS 3.x uses PAPPL 2.x which has different operations and attribute names (as part of standardization in the PWG) but otherwise works similarly.
> 
> The Create-Printer operation accepts the "smi55357-device-uri (uri)" and "smi55357-driver (keyword)" operation attributes to provide the device URI and model/driver name, and cupslocald (from the cups-local project) supports the following driver names:
> 
> - 'everywhere': IPP Everywhere/AirPrint/Mopria/Wi-Fi Direct printer
> - 'pcl': Generic B&W PCL printer
> - 'pcl_duplex': Generic B&W PCL printer with 2-sided printing support
> - 'ps': Generic B&W PostScript printer
> - 'ps_duplex': Generic B&W PostScript printer with 2-sided printing support
> - 'ps_color': Generic Color PostScript printer
> - 'ps_color_duplex': Generic Color PostScript printer with 2-sided printing support
> 
> The PCL and PostScript drivers are extremely limited and are just there to support legacy Samba printing basic support for local (typically enterprise) laser printers.
> 

So when I send a Create-Printer request to a CUPS 3.x daemon (both local and 
sharing) an entry in a profile (~/.cups/profiles/ or /etc/cups/profiles/*, 
latter only for sharing server) is created?

>> If I have only the local server, it is stateless, it only uses temporary queues.
> 
> It is not stateless.  It just doesn't have permanent queues and doesn't share local queues with other systems.
> 
>> How do I, in case of not using mDNS/DNS-SD, tell my discoveries/manual IP selections to the local server so that it sticks with them? Or am I REQUIRED to use mDNS/DNS-SD when I have a system with only the local server of CUPS 3.x as print environment?
> 
> We have been talking about this ("printer profiles") for a very long time:
> 
>      https://github.com/OpenPrinting/cups-local/issues/2
> 

OK, so they also work with the local server.

So this means that our printer setup tool which Abdelrahman is working on 
creates entries in the profile when manually adding print destinations, either 
if mDNS/DNS-SD is not used or when the printer is outside the local network 
(VLAN or so)?

OK, so we need to settle on a format for this file so that Abdelrahman can 
implement that.

>> Or do I have to use the sharing server when I just want to print locally but not use mDNS/DNS-SD? Does the sharing server has a config file for holding such printers?
> 
> The sharing server is more of a traditional "all queues are permanent" service and saves the queue state/configuration across runs.
>

Does the sharing server not get its queues the same way as the local one, both 
by discovering printers via mDNS/DNS-SD AND including destinations by entries in 
the profile (which can be system-wide now)? And it adds rules for how to share 
these printers also in the profile?

    Till