Starting daemons after install not always what the user wants, but what/how to do ?

2006-09-25 Thread Mike Hommey
Some programs may be used as system daemons, but can also be used by a user for some other purpose. For example, fetchmail can be used as a system-wide mail fetcher, but can be used and configured by a user to fetch his own mail, through his own setting. Now, let's say someone creates some

Re: Starting daemons after install not always what the user wants, but what/how to do ?

2006-09-25 Thread Sam Morris
On Mon, 25 Sep 2006 19:59:06 +0200, Mike Hommey wrote: There is gnome-user-share, that uses apache2 to set up a web dav share on some random high port and make it available as a zeroconf service through avahi. The package depends on apache2. Thus, when installing gnome-user-share, while the

Re: Starting daemons after install not always what the user wants, but what/how to do ?

2006-09-25 Thread Mike Hommey
On Mon, Sep 25, 2006 at 07:03:03PM +, Sam Morris [EMAIL PROTECTED] wrote: IMO, packages where there is a need for this functionality should be split as above. For example, fetchmail-daemon (containing the init script) which depends on fetchmail; spamassassin-spamd depending on spamassassin;