On Fri, Sep 18 2009, Steve Langasek wrote:
>>>> Hmm. You do have a point. However, the original use case was
>>>> for a package to be able to have it's log files rotated periodically,
>>>> and by that criteria cron, anacron, fcron, and bcron do fit the bill.
>>>>
>>>> I think perhaps we need to pare down the requirements (and
>>>> perhaps change the name of the virtual package), so that packages that
>>>> just want a periodic job scheduler don't have to specify a list of
>>>> matching providers.
>>>>
>>>> Requirements:
>>>> 1) Be able to run a batch job periodically.
>>>> 2) Correct execution of /etc/cron.{hourly,daily,weekly,monthly}
> On Thu, Sep 17, 2009 at 09:03:22AM +0000, Gerrit Pape wrote:
>> On Wed, Sep 16, 2009 at 10:32:04PM -0700, Steve Langasek wrote:
>> > fcron doesn't appear to run cron.daily by default, and neither does bcron.
>> > *Only* the cron package ships a crontab that runs /etc/cron.daily by
>> > default; anacron also supports running cron.daily, but relies on cron
>> > itself
>> > to trigger it on a daily basis. (Without cron installed, anacron will only
>> > rotate logs when you reboot.)
>
>> Hi, the bcron-run package provides /etc/crontab, which includes
>
>> 24 4 * * * root test -x /usr/sbin/anacron || run-parts --report
>> /etc/cron.daily
>
> Ok, then the bcron-run package (but not the bcron package) would meet that
> requirement.
So. We have a criteria that would allow for anyone needing to
set up a periodic cron job, and at least two packages that provide such
functionality: cron, and bcron-run.
Is this sufficient to add a virtual package?
manoj
--
The little pieces of my life I give to you, with love, to make a quilt
to keep away the cold.
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
