Skip Menu |

This queue is for tickets about the POE-Component-Cron CPAN distribution.

Report information
The Basics
Id: 44442
Status: resolved
Priority: 0/
Queue: POE-Component-Cron

People
Owner: Nobody in particular
Requestors: dolmen [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.019
Fixed in: (no value)



Subject: Extract the generic scheduling to a sparate dist with less dependencies
Extract the parts of POE::Component::Cron that are non-cron dependent to a separate distribution to avoid many requirements (Set::Crontab, DateTime::Event::Cron, DateTime::Event::Random) that are not needed if from_cron() is not used. I'm using PoCoCr with my own DateTime::Set not based on DateTime::Event::Cron so the module has dependencies that are useless for me. Suggested plan: - Create a distribution POE::Component::Scheduler which contains all current POE::Component::Cron except 'from_cron' - Rewrite PoCoCr to use POE::Component::Scheduler : all methods will be forwarded to POE::Component::Scheduler, only from_cron would be added.
Subject: Re: [rt.cpan.org #44442] Extract the generic scheduling to a sparate dist with less dependencies
Date: Mon, 23 Mar 2009 14:56:18 -0600
To: bug-POE-Component-Cron [...] rt.cpan.org
From: chris fedde <chris [...] fedde.us>
I like this refactoring idea. I'd be happy to let PoCoCron become the jumping off place for a new distro that does not include the cron stuff. PoCo::Schedule seems like a good name. If such a module were to magicaly appear in CPAN I might re-write PoCo::Cron to depend on it :-) I'm not sure that I'll have time to get around to implementing it real soon myself. 2009/3/20 Olivier 'dolmen' Mengué via RT <bug-POE-Component-Cron@rt.cpan.org Show quoted text
>
Show quoted text
> Fri Mar 20 12:10:09 2009: Request 44442 was acted upon. > Transaction: Ticket created by DOLMEN > Queue: POE-Component-Cron > Subject: Extract the generic scheduling to a sparate dist with less > dependencies > Broken in: 0.019 > Severity: Wishlist > Owner: Nobody > Requestors: dolmen@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=44442 > > > > Extract the parts of POE::Component::Cron that are non-cron dependent to > a separate distribution to avoid many requirements (Set::Crontab, > DateTime::Event::Cron, DateTime::Event::Random) that are not needed if > from_cron() is not used. > > > I'm using PoCoCr with my own DateTime::Set not based on > DateTime::Event::Cron so the module has dependencies that are useless > for me. > > > Suggested plan: > - Create a distribution POE::Component::Scheduler which contains all > current POE::Component::Cron except 'from_cron' > - Rewrite PoCoCr to use POE::Component::Scheduler : all methods will be > forwarded to POE::Component::Scheduler, only from_cron would be added. >
Le Lun. Mar. 23 17:03:13 2009, CFEDDE a écrit : Show quoted text
> I like this refactoring idea. > I'd be happy to let PoCoCron become the jumping off place for a new distro > that does not include the cron stuff. PoCo::Schedule seems like a good > name. If such a module were to magicaly appear in CPAN I might re-write > PoCo::Cron to depend on it :-) I'm not sure that I'll have time to get > around to implementing it real soon myself.
PoCo::Schedule did magically appear ;) I've setup a Google Code project at http://code.google.com/p/poe-component-schedule/ and I would be glab if you applied as co-maintainer.
Subject: Extract the generic scheduling to a separate dist with less dependencies
I've released POE::Component::Schedule 0.03 which has a more complete test suite than PoCo::Cron. Closing the bug.