[bug #64619] [mdoc] allow distros to maintain mdoc strings

[Ingo Schwarze]

Follow-up Comment #4, bug #64619 (project groff):

Not sure why you interpret

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273903

as being mad.  That's merely a list of things FreeBSD needs to deal with when
upgrading to groff-1.23, and it happens to be public.  It's normal that a
major version upgrade of software that is actively used requires some work. 
For upgrading groff in OpenBSD ports, i know that the list of issues i will
have to deal with will be *much* longer than that, but i'm not planning to
make that list public.

Regarding

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273599

that particular (very minor) issue actually goes away if groff follows my
recommendation of no longer validating OS release numbers.

Regarding colonization, there is a summary at

https://mandoc.bsd.lv/ports.html

Most BSDs plus illumos use mandoc as the formatting engine, but for
apropos(1), man(1), and man.cgi(8), which implementation various BSD systems
use varies wildly.  As far as i'm aware, the only systems using mandoc by
default in *all four* capacities are OpenBSD and Void Linux.

One reason why Wolfram Schneider probably cares about this is that he is the
maintainer of the old Perl4 man.cgi(8) that FreeBSD is still using, and which,
i believe, is running groff under the hood:

https://man.freebsd.org/cgi/man.cgi/source




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64619>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/