So.... does the solution suggested by the SavaPage developer make sense? Or is it against the NS philosophy on how to handle systemd services?
Can we expect any form of problems if the SavaPage install disables the default CUPS service and creates it's own savapage.cups.service?
As said, the idea is that IF the NS printermodule (that installs CUPS and cups.service) gets an update, the savapage install doesn't break, and the SavaPage install doesn't change the default cups.service (it disables the service instead)
I think we can safely assume that if someone installs SavaPage to manage all printing, standard printqueue's are not used anymore, all printing will be handled by SavaPage.
I will ask confirmation when de-installing SavaPage, the default cups.service will be reactivated.
It would be nice if the install howto gets tested by others. Please confirm or add suggestions for changes.