svn commit: r535779 - in head/net/openntpd: . files
Adam Weinberger
adamw at adamw.org
Thu May 21 23:30:48 UTC 2020
> On May 21, 2020, at 09:35, Christian Weisgerber <naddy at mips.inka.de> wrote:
>
> Adam Weinberger:
>
>>> Author: naddy
>>> Date: Mon May 18 19:36:51 2020
>>> New Revision: 535779
>>> URL: https://svnweb.freebsd.org/changeset/ports/535779
>>>
>>> Log:
>>> Add a note in pkg-message that you need to override the manual search
>>> path to view the correct ntpd(8) man page.
>>
>> Is there value to installing the manpage as openntpd.1, or creating
>> that as a symlink?
>
> Then you have a man page whose name is different from the command it
> describes. Of course, sbin/ntpd could be renamed to sbin/openntpd.
> But how about ntpd.conf, ntpctl? This just keeps spiralling.
>
> I'll note that net/ntp and net/ntpsec conflict even more with base
> ntp. Should those be renamed as well?
>
>> It'd work around that underlying problem, and
>> frankly `man openntpd` is the first place I inevitably look for
>> openntpd's manpage.
>
> When you install security/openssh-portable, do you try "man openssh"?
> net/isc-dhcp44-*?
>
> How to deal with ports that install components that have name
> conflicts with the base system is a general problem, and there
> doesn't seem to be a good solution.
>
> I don't like pkg-message either, but bjk@ suggested it.
> https://lists.freebsd.org/pipermail/freebsd-doc/2020-May/034062.html
>
> If it upsets the status quo too much, I'll happily revert it.
It’s not about status quo, and there’s no problem. I had a thought about supporting end-user experience so I shared it with you. You’re the maintainer so it’s all up to you.
# Adam
—
Adam Weinberger
adamw at adamw.org
https://www.adamw.org
More information about the svn-ports-all
mailing list