Chris Adams wrote:
Once upon a time, Mathieu Bridon (bochecha) <bochecha@xxxxxxxxxxxxxxxxx> said:
If name clashing is a real problem
then the upstream project should decide how/what to rename it too.
Of course upstream should decide and the review requester is supposed to
bring this problem up there.
This looks to me like the "sendmail" command. Isn't it a rather
generic name for a command ?
But it can be provided by several packages, and we use the
alternatives system for that.
Couldn't we do the same for calendar ?
Is this "calendar" the same as:
calendar - Writes reminder messages to standard output
If so, that is the program name, and it should stay. I've got it on
Tru64 Unix (which is BSD derived from many years ago) as a standard part
of the OS.
Is somebody next going to say "ed" has to be renamed because there are
other editors?
Yes, this is the calendar command you are thinking of. It prints
reminder messages and can easily be dropped in to cron. It's been a
standard part of BSD for quite some time, but Linux has lacked an
equivalent.
I have taken this command from the OpenBSD source repository and patched
it for Linux. So, upstream for this command is not going to change the
name (as suggested by some other people).
The name of the program has always been 'calendar'.
--
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
