updating cron and atrun

[Xin LI]

On Mon, Feb 10, 2020 at 1:38 PM Simon J. Gerraty via freebsd-arch <
freebsd-arch at freebsd.org> wrote:

> Josh Aas <josh at kflag.net> wrote:
> > FreeBSD. I'm curious to hear if there are actual technical reasons
> > that it's worthwhile for FreeBSD to do it.
>
> Reduce the friction of people moving from other systems to FreeBSD?
>
> > considering. In an earlier email you said "People generally have no
> > idea what they do and people are unwilling to chance using them or
> > learning something new..." That doesn't sound like a description of
> > "basic functionality" that necessarily needs to be a part of a base
> > operating system.
>
> The whole argument about what the masses grok would lead everyone to
> adopt Windows.
>
> I've used at(1) extensively in the past, I consider it basic
> functionality.
>

+1.

Also note that it's not something that is high effort at all, because
others have already implemented it, and did so in less than 700 lines of
code, with license block included.  I'd say bringing OpenBSD cron is a low
hanging fruit if someone wants to do something in the project, and IMHO
there is no reason to remove the functionality because of that.

I have worked on bringing OpenBSD cron to FreeBSD a while ago (I think it
was ~2012) but never committed it because subversion made my life hard
(well, partially -- I should have created a branch on user/ but I didn't)
to keep my local patches on the move to the point that eventually I have
gave up maintaining it.

Cheers,