Refactoring calendar(1) (was: svn commit: r365984 - head/usr.bin/calendar/calendars)

[Greg 'groggy' Lehey]

On Thursday, 24 September 2020 at 14:35:10 -0700, Cy Schubert wrote:
> In message <202009241555.08OFtjKx047062 at gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
>> -- Start of PGP signed section.
>>> [Trimmed]
>>>
>>> People, please adjust your posts.  It's hard fighting your way through
>>> a lot of expired verbiage.

Thanks for the trimming.

>>> While I have your attention, does anybody think that the -a option of
>>> calendar(1) is worth keeping?  It goes through *all* calendar files on
>>> a system and mails them to the owner.  It has the interesting side
>>> effect (we wouldn't want to call it a bug) that root gets three copies
>>> (one each for root, toor and daemon).  I can't see anything useful
>>> there that a per-user cron job can't do.
>>
>> What the per-user cron job does is create a larger workload for
>> systems that are expecting all users to be running calendar, as
>> possible in an acedemic system which each student has a login.
>
> Have it use libxo might be a good exercise for someone wanting to get back
> into it after a while, or a student.

How would that address the issue?

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20200925/44c89c11/attachment.sig>