News for hackers. Stuff that matters.
Re:Install Debian packages without starting daemons by fsniper on Friday June 27, 2014 @11:43AM (#7954484)
I really like the way it's now. But in some edge cases you need the service stopped in the first place.

For example RabbitMQ initiates a database which denies cluster configurations if intact. So in Debian way if you are using some configuration management tool to start a RabbitMQ cluster you have install/stop/resetdb/restart cycle which is prone to failing.

So some edge cases need this kind of 2cents.

Re:Install Debian packages without starting daemons by atoponce on Friday June 27, 2014 @11:49AM (#7954530)
This is why upstream developers should use /etc/default/ to place daemon configuration files into. Then the configuration file could have "START=no", and even though the policy would start the daemon by default, the upstream developer could prevent this from happening.
Re:Install Debian packages without starting daemons by regularfry on Sunday June 29, 2014 @09:57AM (#7961181)
> This is why upstream developers should

Eh, not so much. Any system which tries to convince upstream to change their ways is going to be fraught, so we're always going to need another way to force the behaviour we want in spite of the upstream.

Re:Install Debian packages without starting daemons by fsniper on Saturday June 28, 2014 @08:40PM (#7959931)
But if it's not covered yet rc-d policy would help.