libschedule-cron-events-perl 1.96-2 source package in Ubuntu
Changelog
libschedule-cron-events-perl (1.96-2) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.6.1, no changes needed. -- Jelmer Vernooij <email address hidden> Sat, 19 Nov 2022 19:07:44 +0000
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Oracular | release | universe | misc | |
Noble | release | universe | misc | |
Mantic | release | universe | misc | |
Lunar | release | universe | misc |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libschedule-cron-events-perl_1.96-2.dsc | 2.2 KiB | 71c98d481572a582f8d268c3154af5f1587f91e547a6f4b234c55c36cf6d521c |
libschedule-cron-events-perl_1.96.orig.tar.gz | 25.2 KiB | cafafea2812af28a06009cb6dfce845e2a5215b7d2d726e212081fac8ec1f991 |
libschedule-cron-events-perl_1.96-2.debian.tar.xz | 2.5 KiB | 02a9115c4196e3ce10319ef58adc8f4f05d15283ff233b11aa563cd982414c75 |
Available diffs
- diff from 1.96-1 to 1.96-2 (625 bytes)
No changes file available.
Binary packages built by this source
- libschedule-cron-events-perl: module to find out the times at which a cron entry would run
Given a line from a crontab, tells you the time at which cron will next run
the line, or when the last event occurred, relative to any date you choose.
The object keeps that reference date internally, and updates it when you call
nextEvent() or previousEvent() - such that successive calls will give you a
sequence of events going forward, or backwards, in time.
.
Use setCounterToNow() to reset this reference time to the current date on
your system, or use setCounterToDate() to set the reference to any arbitrary
time, or resetCounter() to take the object back to the date you constructed
it with.
.
Schedule::Cron:: Events uses Set::Crontab to understand the date
specification, so it should be able to handle all forms of cron entries.