From owner-freebsd-arch@freebsd.org Wed Sep 23 23:07:17 2020 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD2F23E164F for ; Wed, 23 Sep 2020 23:07:17 +0000 (UTC) (envelope-from grog@lemis.com) Received: from lax.lemis.com (www.lemis.com [45.32.70.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4BxYjJ2TKFz4VYJ for ; Wed, 23 Sep 2020 23:07:16 +0000 (UTC) (envelope-from grog@lemis.com) Received: from eureka.lemis.com (aussie-gw.lemis.com [167.179.139.35]) by lax.lemis.com (Postfix) with ESMTP id 9F3B228034; Wed, 23 Sep 2020 23:07:09 +0000 (UTC) Received: by eureka.lemis.com (Postfix, from userid 1004) id E620926359A; Thu, 24 Sep 2020 09:07:08 +1000 (AEST) Date: Thu, 24 Sep 2020 09:07:08 +1000 From: Greg 'groggy' Lehey To: freebsd-arch@freebsd.org Cc: Warner Losh , Shawn Webb Subject: Refactoring calendar(1) (was: svn commit: r365984 - head/usr.bin/calendar/calendars) Message-ID: <20200923230708.GA53226@eureka.lemis.com> References: <20200923134334.czblcl2ppyxjnigs@mutt-hbsd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: http://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) X-Rspamd-Queue-Id: 4BxYjJ2TKFz4VYJ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of grog@lemis.com has no SPF policy when checking 45.32.70.18) smtp.mailfrom=grog@lemis.com X-Spamd-Result: default: False [-3.72 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.96)[-0.955]; FREEFALL_USER(0.00)[grog]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.91)[-0.910]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[FreeBSD.org]; AUTH_NA(1.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.05)[-1.053]; SIGNED_PGP(-2.00)[]; FORGED_SENDER(0.30)[grog@FreeBSD.org,grog@lemis.com]; RCVD_NO_TLS_LAST(0.10)[]; R_SPF_NA(0.00)[no SPF record]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20473, ipnet:45.32.64.0/19, country:US]; FROM_NEQ_ENVFROM(0.00)[grog@FreeBSD.org,grog@lemis.com]; MAILMAN_DEST(0.00)[freebsd-arch]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2020 23:07:17 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [Trimmed] People, please adjust your posts. It's hard fighting your way through a lot of expired verbiage. On Wednesday, 23 September 2020 at 9:18:27 -0600, Warner Losh wrote: > On Wed, Sep 23, 2020 at 7:43 AM Shawn Webb > wrote: > >> Would it make sense to prune calendar entries to only BSD-related >> entries? > > Fortunately, I have already contacted grog@ directly. He was quite > receptive to my email suggesting something be done. After a couple of > rounds, there's the rough plan we're talking about. Briefly: > > 1. ... > > So, it's just an outline at this time, which is why I hadn't sent a > concrete proposal here just yet. Wanted to at least get a list of > the files that would remain so we can have an intelligent discussion > about those, but since this showed up I thought I'd send a heads up > so people know what's going on. The real issue is: what do we remove? Summarizing imp@'s points, I think that the base functionality of calendar(1) should stay, and so should the FreeBSD-related calendar files. There's really a question as to whether the non-FreeBSD related ones should remain anywhere (including as a port). As somebody said, they're a relict of a bygone day, and some are very inaccurate. I seem to be the only one maintaining them, and even that is not without criticism. It might be a better idea to write a completely new port that sucks in calendar entries from *somewhere* and makes BSD-compliant calendar files out of them. So, as imp@ says, it would be good to discuss which files should go and which should remain. 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. 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 --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAl9r1RwACgkQIubykFB6QiM1YwCfeuaV6Q97r1QVfKWdorWFxqnk w2oAniofsf5teeBj1J4LJwYs8roOGs/q =gAOt -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--