Re: debian-policy: New virtual package: cron-daemon
On Sun, Oct 08, 2006 at 09:48:01PM +0200, Clément Stenac wrote: > Hi, > > > [ Debian-specific feature ] > > - Correct execution of /etc/cron.{hourly,daily,weekly,monthly} > > Don't we support these by using entries in /etc/crontab and run-parts > for all cron systems, which would make this requirement void ? 'We' as in Vixie Cron? Yes, but I want to list it explicitly since /etc/crontab is shipped by cron and I would not consider a replacement that did not execute the scripts there (imagine a replacement that shipped an empty /etc/crontab or did not ship one at all [1]). Notice that there's is nothing preventing a cron replacement to handling those directories by itself natively (i.e. without using /etc/crontab lines). Regards Javier [1] Of course, if /etc/crontab were provided as a configuration file of a different (standard) package this issue would be side-stepped. signature.asc Description: Digital signature
Re: debian-policy: New virtual package: cron-daemon
On Sunday 08 October 2006 21:05, Javier Fernández-Sanguino Peña wrote: > I propose re-adding 'cron-daemon' with the following requirements (that > will need to be written down similarly to the 11.6. section "Mail > transport, delivery and user agents"): Maybe add: - should be able to work nicely with anacron I realize that this is really the other way around and that it is probably not much of an issue, but still something to keep in mind. pgp50EiNMh7hQ.pgp Description: PGP signature
Re: debian-policy: New virtual package: cron-daemon
Hi, > [ Debian-specific feature ] > - Correct execution of /etc/cron.{hourly,daily,weekly,monthly} Don't we support these by using entries in /etc/crontab and run-parts for all cron systems, which would make this requirement void ? -- Clément -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-policy: New virtual package: cron-daemon
Package: debian-policy Priority: wishlist Hi all, It was suggested to me (#349170) that we should use a virtual package 'cron-service' to make it easier to people to switch between different cron implementations. Currently in Debian there are three of them available: vixie-cron, which is our current standard, fcron and bcron (Bruce's cron). Many packages that currently depend on 'cron' depend on 'cron | bcron', if a new cron replacement (such as mcron, xcron, chronic or upstart) gets into Debian all those packages need to be modified to Depend on: 'cron | bcron | fcron | mcron | upstart | chronic', making transitions a pain and forcing admins to play with the package system to satisfy dependancies. Now, we *used* to have a 'cron-daemon' virtual package but it was removed from Debian policy (in version 3.6.2.2) since the previous cron maintainer wanted policy to clarify what it should 'mean' (see #257726) I propose re-adding 'cron-daemon' with the following requirements (that will need to be written down similarly to the 11.6. section "Mail transport, delivery and user agents"): [ POSIX ] - Has to provide /usr/bin/crontab and support crontab entries [ Implemented in most Linux / BSD distributions, including Debian, but not in Solaris, HP-UX or AIX's cron ] - Correct execution of /etc/cron.d - Correct support of /etc/crontab - Correct support of /etc/cron.{allow,deny} - Has to support 'crontab -u' - Support of crontab entries with extended features (i.e. those in Vixie Cron need to be supported), these include names for days and months, ranges, step values and the 'special strings' (@reboot, @yearly..) [ Debian-specific feature ] - Correct execution of /etc/cron.{hourly,daily,weekly,monthly} Does anyone oppose this new virtual package? Javier PS: Debian-policy people, please CC: me on replies signature.asc Description: Digital signature