On Wed, Apr 01, 2009 at 05:38:29PM +0200, Josselin Mouette wrote: > Le mercredi 01 avril 2009 à 17:03 +0200, Patrick Schoenfeld a écrit : > > * We add a new configuration file (possibly /etc/rc.conf because thats > > a file that exists in different distributions and has a similar meaning) > > which can have the following configuration settings: > > > > * RUN_NEW_SERVICES_AFTER_INSTALL=<yes|no|1|0|true|false> > > * RUN_<SERVICE>=<yes|no|1|0|true|false> > > > > This configuration file must not be modified by maintainer scripts. > > The rationale for the RUN_<SERVICE> entries is that an admin can have > > RUN_NEW_SERVICES_ON_INSTALL=false, but decide for a certain service > > that it shall start after he installed it before. > > I think it is a bad idea to specify system-wide whether certain services > can be enabled or not.
Well, its only about *new* services after installation. The intention behind that is that some people don't like to run un- or half-configured daemons immediately after installing them. The idea is to support whatever the admins wants to choice, which seems good to me. > Some services absolutely need to be running when they are installed, to > satisfy dependencies (think D-Bus or HAL). Some services cannot run > before they are configured (think a firewall). Yeah, right. But those are special cases that should be handled accordingly and don't need to stop us from aiming at a homogenization of services control. > I like the homogenization part of your proposal, but the default policy > should be set by packages themselves, not by the local administrator. Well, thats an opinion I can't agree less with. Yes, I accept that there are special cases, but the default really should be that the admin has the last word. Best Regards, Patrick -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org