The core component of quassel only ships the init script for openrc. It should include a systemd service, too. Reproducible: Always Steps to Reproduce: emerge quassel with core enabled and try to start it with systemd as your init system. Actual Results: no service for quassel available Expected Results: service for systemd shipped with quassel ebuild
Created attachment 375498 [details] systemd service unit for quassel core Thanks to thomasg from #gentoo.de for providing this service file ! It currently depends on postgresql, because it is one of (three?) possible sql backends (sqlite, mysql, postgresql) for quassel core. Maybe gentoo should ship a service template and set the appropriate dependencies in the service file according to the USE of quassel. Modify it as needed for you sql backend.
Actually there are some errors in that service file. I will upload a better one in a few days. I don't have enough time to test this right now.
Drop the EnvironmentFile and related variables. Also drop the postgres stuff. If the sysadmin wants to change those values or use postgres, he is going to have to tweak the unit file by copying it to /etc/systemd/system or overriding values via /etc/systemd/system/quassel.service.d.
Also, you don't need PIDFile for a non-forking service.
+*quassel-0.10.0-r1 (02 May 2014) + + 02 May 2014; Pacho Ramos <pacho@gentoo.org> +files/quasselcore.service, + +quassel-0.10.0-r1.ebuild: + Add unit file (#508450 by Konstantin) +
Just for the record. + + 03 May 2014; Johannes Huber <johu@gentoo.org> -quassel-0.10.0.ebuild, + quassel-9999.ebuild: + Add systemd unit file to live ebuild as well, bug #508450. Remove old. +
