On Tue, 2004-03-30 at 16:08, Zefram wrote: > Patrice Fortier wrote: > Therefore, I suggest that we separate each of these daemon packages into > two, one that provides the daemon software and a separate one to run it. > That way those of us who want to install a daemon and use it in our own > way would not be hampered by someone's idea of how the daemon should > normally be run. And where the daemon is packaged with a client, > installing the client wouldn't cause an unwanted daemon to run. Why splitting? How about a unified system, eg. each init script sources a config file from /etc/default, where you have a simple line like START_FOO=yes > Example: the "ssh" package would, as now, provide both the ssh client > and ssh server, but wouldn't contain an init script. There would be a > separate "ssh-daemon" package, with a dependency on the "ssh" package, > and containing an init script. IMHO shipping packages with just an init script is bloat. > Debian should ship with *no* network daemons listening by default. > I'm rather surprised that it hasn't adopted this policy already. I agree. Greetings, Oliver
Attachment:
signature.asc
Description: This is a digitally signed message part