https://bugzilla.novell.com/show_bug.cgi?id=860340 https://bugzilla.novell.com/show_bug.cgi?id=860340#c0 Summary: Reconsider Backward compatibility in openSUSE:Systemd packaging guidelines Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other URL: http://en.opensuse.org/openSUSE:Systemd_packaging_guid elines#Backward_compatibility OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: fs@suse.com ReportedBy: mt@suse.com QAContact: adrian@suse.com CC: lnussel@suse.com, stefan.fent@suse.com, werner@suse.com, systemd-maintainers@suse.de Found By: --- Blocker: --- I've no idea if this bug is assigned correctly... PM? The systemd packaging guidelines enforce ("you have to") a rc<servicename> -> $sbin/service compatibility link causing bug reports which force packagres to create such links or implement a very specific wrapper to provide the possibility to handle a service via (IMO) the SUSE specific "rc<servicename>", On the one side there are feature requests enforcing that service have to provide native systemd support or features requiring it, on the other side "it has to work as before". Please rethink this requirement. There are many different services. Some service have switched to per instance start of services using native systemd mechanisms instead of handling all instances in one service and a target which handles all instances (e.g. bug#848070), .. or have been reworked otherwise. Please review all the /etc/rc.status, /sbin/service (can't handle targets grouping multiple instance services) and all other hooks redirecting to systemctl, decide which mechanisms are required, define and document applicable rules and cleanup all the rest. -- 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.