Date: Sun, 21 May 2017 17:20:10 -0500 From: "Mike Karels" <mike@karels.net> To: "Benjamin Kaduk" <bjk@FreeBSD.org> Cc: "Baptiste Daroussin" <bapt@FreeBSD.org>, arch@FreeBSD.org, doc@FreeBSD.org, current@FreeBSD.org, doceng@FreeBSD.org Subject: Re: The future of the roff toolchain Message-ID: <C47D62E3-6E5E-48FF-9726-4745E7149A23@karels.net> In-Reply-To: <20170521203640.GR39245@kduck.kaduk.org> References: <20170521125733.bmd4tmq6iqpsbvgl@ivaldir.net> <20170521203640.GR39245@kduck.kaduk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 May 2017, at 15:36, Benjamin Kaduk wrote: > On Sun, May 21, 2017 at 02:57:33PM +0200, Baptiste Daroussin wrote: >> >> What I want to propose now, it to render them as PDF (html?) once and >> push them >> somewhere (to be defined) as static document on our documentation >> website. >> Please doceng@ provide me a location where to push them. >> >> And then remove bsd.doc.mk from FreeBSD 12.0 along with the removal >> of groff. >> I also want to remove most of roff related tools (the one provided by >> toolchains >> available in ports) for which we kept a BSD version (not really >> maintained in >> base): >> namely: >> - checknr >> - vgrind >> - colcrt >> >> Only keeping: >> - col (useful in other places than roff) >> - soelim (also used for manpages and we have a clean BSD licensed >> version which >> is also now parts of mandoc) > > That sounds like a good plan to me. Thank you for putting in all > the time trying out the alternate roff toolchains! +1. I agree that /usr/share/doc is strictly legacy; only the man pages matter for base. > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to > "freebsd-arch-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C47D62E3-6E5E-48FF-9726-4745E7149A23>