Goal is to make cups installed as snap to be available for applications to print on it
The “control” in cups-control is there because snaps can run as root, and that gives connected snaps full administrative capabilities via the cups socket
We might have a “cups” interface that bind-mounts /etc/cups/client.conf when connected
Classic applications would not see that file, though, and wouldn’t be able to print into the snapped cups
The cups snap can also try to allocate port 631 by default anyway, and make itself available for printing for the whole system
Another more complex alternative:
Cups is able to chain two cups installation together; easiest is probably to allow the cups snap to cups-control the system cups, and make itself available for printing automatically
Apparently some of that already works today with the snap, but it might be automated further to make the process less painful for users
