From: Stu <stu@...>
Date: 2013-05-30T08:15:55+09:00
Subject: Re: GEMs pollution or not?

Not sure what your question about the repository is. I imagine if your
referring to rubygems.org someone owns the name cron already so you
may have to use a different name or namespace it.

As far as the decoupling question think what cron really is. It's a
higher level job scheduler which parses a table created by the user
(i.e. crontab) to provide periodic automation of system level tasks
(i.e. clean core dumps, clean /tmp check filesystem healths and so
forth). Cron is built on top of at which is basically a procedure
queue for running processes at set time. Cron is also the daemon
whereas both at and batch commands are  The at command utilized the
unix date and mail commands. Break it down per function for your
abstraction: cron is your daemon, at is your scheduler, calender
(date) is an interface which both at and cron will depend on. by
having the separate modules for each will aid in the re-usability your
looking for and also reveal the UNIX philosophy as well. Another
command to look at implementing would be the jobs command which acts
as a superviser for your processes state.

Happy Hacking!

~Stu