3 ms·
When packaging a daemon for Debian, the maintainer should add sufficient questions during installation, and sane default values, to start the service. Contrary
by belorn 13y ago
When packaging a daemon for Debian, the maintainer should add sufficient questions during installation, and sane default values, to start the service.
Contrary to the article, I think this is a rather good policy. It makes sure packages are usable as they are, rather than the normal process of config, make, make-install, and last adding user configuring before anything will start up. Debian is not Gentoo.
For those daemons which this isn't possible, package maintainers has a harder time. One of the better ways is simply to have it run, but in a safe way which do nothing. That would solve the issues the article describes, and would not be harmful.
- stephen_g 13y agoWhat does packages using non-standard hacks that break puppet scripting have to do with configuring and building source code? That's not related to the issue at all...
- belorn 13y agoThe article talks about two issues. One is that debian has policy to default run daemons after installation. The second issue the article brought it up is the issues with puppet. Regarding the first issue, sane defaults and usable packages directly after installation came as a result of the config, make, and make-install process. Users should get a useful package directly without needing to spend days adding all the default settings to start a simple mail or web daemon. The second issue has nothing to do with config, make, and make-install. It has to do with non-standard hacks. If nagios3 had simply started up like apache, this would have been a non-issue.
- _pmf_ 13y ago> One of the better ways is simply to have it run, but in a safe way which do nothing. That would solve the issues the article describes, and would not be harmful. I'd argue it would be worse. I'd rather have the program not run at all than have it preconfigured in a way that contradicts its regular operation and having to reconfigure it to make it work normally.
- belorn 13y agoIf you have to configure it in such way that it can't be done through sane defaults and install questions, then there are no normal operation. Any configuration is going to be unique to that installation. As such, there is no sane configuration that contradicts its "regular" operation, if there is no regular operation to begin with. Apache is a typical example here, as default installation provide no personal website, no web frame work, no kind of web site to speak of. Default here, is to do basically nothing and wait for the user to configure and install.