svn commit: r553259 - in head/deskutils/calendar: . files

[Cy Schubert]

In message <20201026030214.GC19841 at eureka.lemis.com>, "Greg 'groggy' Lehey" 
wri
tes:
> 
>
> --Md/poaVZ8hnGTzuv
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Sunday, 25 October 2020 at 18:37:34 -0700, Cy Schubert wrote:
> > In message <20201026012126.GB19841 at eureka.lemis.com>, "Greg 'groggy' Lehey"
> > wri
> > tes:
> >>> Anticipating the next step: removal of calendar from base, entirely.
> >>
> >> It's a bit late for that.  We discussed this at length (too much
> >> length for some people) on arch@, and we came to the agreement that
> >> the base calendar(1) is a Good Thing, and only the data files needed
> >> to go somewhere where they can be shared amongst projects.
> >>
> >> FWIW, *all* OSs that I've seen, with the possible exception of
> >> Microsoft, have calendar(1).  It serves a useful purpose.  What's your
> >> problem with it?
> >
> > The Linux distros I know of don't provide it, even as an optional RPM.
>
> The machine I have access to, running Debian Testing, has it
> apparently as a standard installation.  Nobody on the system had asked
> for it.  But yes, I was surprised, too.

At $JOB we maintain about 1500 Linux, Solaris and AIX servers, with a few 
Linux and FreeBSD appliances, the remaining 8000 being Windows and a 
growing number of OpenShift containers of which I lost count. The 
workstations are gone, though many of us propeller heads still maintain 
VirtualBox VMs for our own use. (I personally rather use git on a Linux or 
FreeBSD machine than on Windows -- management decision.)

Why I mention all the details above is that my clients never ask for a 
calendar utility. Their contractors who develop containers haven't either. 
That world is gone.

>
> > IMO it's usefulness is questionable, especially with the multitude
> > of tools that already do the same thing.
>
> There is?  I haven't found anything similar.  That was one of the
> things we discussed on arch@, but we came up empty-handed.  If you
> could come up with links, that would be very useful.

Today's tools use iCalendar files and protocols.

For me personally I haven't used a calendar on a UNIX system for 10-15 
years. Personally, I'm more mobile. The data in calendar(1) were a novelty 
at one point, not so much any more.

I see the direction we are in at $JOB, providing bare bones servers for our 
customers and now with the Cloud group providing an even bearer bone 
platform that I see FreeBSD probably following suit by pushing some less 
critical or less used tools to ports and optional packages in pkgbase.

My vision is a smaller more compact FreeBSD in which groups of packages are 
selected to build a system. I also see a blending of pkgbase and ports to 
provide the end user with something more like the Linux server and desktop 
variations based on groups of packages. Selectable profiles if you may.


-- 
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy at nwtime.org>    Web:  https://nwtime.org

	The need of the many outweighs the greed of the few.