On Fri, Apr 8, 2011 at 6:46 AM, Dieter Plaetinck <dieter@xxxxxxxxxxxx>wrote: > On Fri, 8 Apr 2011 06:45:29 -0400 > Kaiting Chen <kaitocracy@xxxxxxxxx> wrote: > > > On Fri, Apr 8, 2011 at 3:33 AM, Dieter Plaetinck > > <dieter@xxxxxxxxxxxx>wrote: > > > > > > On the other hand this issue could be solved in a different way > > > > without any further discussions. There's a need for installing one > > > > cron daemon, but no need for a default cron daemon. It's pretty > > > > the same issue as with the bootloaders. There's no default > > > > bootloader anymore and currently it doesn't make sense anymore to > > > > define one bootloader as the default, because they all have > > > > different features and it depends on the system configuration > > > > which bootloader is the best. In the development isos AIF asks > > > > the user to choose one of currently two bootloaders (grub and > > > > syslinux), more (grub2 and lilo) could or should be added. And > > > > this bootloader is automatically chosen by AIF in the package > > > > selection. The same could be made for the cron daemons. Put every > > > > cron daemon into [core] and let the user choose his preferred > > > > cron daemon during installation. > > > > > > Can we do the same thing for cron daemons? Don't other packages > > > contain crontab files, or something like that? I.e. is it possible > > > to just swap crons and keep a (stock) Arch system working? > > > If so, it *could* be possible to do what you suggest, but don't > > > forget, Arch primary objective is simplicity, not choice. > > > > > > If there is a cron daemon that does what we need, we should just > > > make it the default, period. > > > > > > > I think we're talking about what the default daemon should be, as in > > the one that comes installed with the system on a clean install. > > Maybe you should actually read the text I quoted. Just a thought. > My mistake, sort of glanced over it too quickly. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/
