On Sun, 1 Mar 2015, Sebastian Harl wrote:
I think that MODE=none should no longer be a valid option when using
systemd as you'd then use 'systemctl disable' instead. I don't know
systemd very well, so there could be other options as well and/or maybe
a way to disable upsmon in systemd by default after installing it.
Maybe ... but what if you want the package to have tools like upsc or
upscmd, but don't need upsmon on the given system? Perhaps a debconf
question of whether to enable the service?
At the very least, failure to start the service, at least if it's
because the service is not configured, does not seem like a good reason
to fail the package install.
This can't be the only package out there that needs configuration before
starting a service. How do those other packages handle this issue?
Anyway, I tend to think that dropping systemd support might still be a
good option but you should talk to the release team before. It would be
great if we can get a fix into testing as a removal would affect other
packages (e.g. collectd) as well.
This sounds like a non-starter. With systemd now the default init, and
a requirement for Gnome (default desktop), making a package like this
incompatible would raise a lot of ire, I think.
--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
