https://bugzilla.novell.com/show_bug.cgi?id=857372
https://bugzilla.novell.com/show_bug.cgi?id=857372#c19
--- Comment #19 from Johannes Meixner
From my point of view this proves that the content in cups.service belongs mostly to "policy".
For me it is a policy to define whether or not the cupsd will be started when a printer device is plugged in or available at boot. In this particular case, when plug in an USB printer starts the cupsd it means any user who can plug in a USB device that claims to be an USB printer can start a daemon process that runs as root. I assume many home-users may like that automatism but perhaps in business environments such automatisms could be scaring? I cannot make such decisions and therefore I cannot maintain the content of systemd unit configuration files for CUPS and accordingly I like to split those files out of the cups package. I am thinking about a new separated source package "cups-systemd" or "systemd-cups" to even more indicate that its content belongs to systemd and not to the actual CUPS software. Basically cups-systemd/systemd-cups should contain as much as possible regarding systemd for CUPS. I think cups-systemd/systemd-cups must have a RPM requirement for cups but cups must not have a RPM requirement for cups-systemd/systemd-cups because the plain CUPS software can run without systemd (without systemd it is up to the admin how to launch cupsd). For cups a RPM recommends for cups-systemd/systemd-cups could be correct or even better only a "Supplements: cups" in cups-systemd/systemd-cups should be sufficient. A more general example why the systemd support pieces should be strictly separated form the actual software: Assume there is an openSUSE contributor who makes a package for his software with an executable /usr/bin/something_useful. Now the openSUSE community decides that /usr/bin/something_useful is great software that should be run as a service. Why does the openSUSE contributor who just made that package now need to worry about systemd and services and openSUSE policies and do all that work to get all what is needed by openSUSE to run his /usr/bin/something_useful as a service into his package? Why cannot openSUSE make a strictly separated package "something_useful-systemd" or "systemd-something_useful" that provides the systemd support pieces for "something_useful"? Even if the one who made the "something_useful" package wants to care about systemd and services and openSUSE policies and do all that work, I think it would be nice when he keeps the systemd support pieces separated form the actual software in a separated package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.