Hi Marc, Marc Espie wrote on Fri, Jun 26, 2020 at 10:43:49PM +0200: > On Tue, Jun 23, 2020 at 12:20:35PM -0600, Theo de Raadt wrote: >> Ottavio Caruso <ottavio2006-usenet2...@yahoo.com> wrote:
>>> Unless I've got it all wrong, <https://man.openbsd.org/> will only >>> display man pages for programs and commands in base. Is there a way to >>> display the man page for a package/port I haven't installed and/or >>> downloaded yet? (This assumes I haven't downloaded the ports cvs >>> tree). >> Doing that would be very annoying and painful, and very few people >> would want it. It would also substantially degrade the clarity at >> man.openbsd.org Which means that *if* we ever do this, it needs to be a separate manpath "ports", "ports-current" or something similar, which would result in URIs like https://man.openbsd.org/ports-current/got.1 > Actually, it ought to be feasible to have the same mechanism in place for > base as a third party mechanism. > > I don't think it would be that difficult to setup, this obviously ought to > be separate from the main OpenBSD installation, as the quality of manpages > from ports is often not up-to-par compared to base. > > Both Ingo and naddy and I, we've been routinely passing all manpages from > all packages through groff and mandoc and makewhatis to the point that > over 99% of them would be clean for a usage similar to man.openbsd.org Actually, you are mistaken here, i have never done that and i wouldn't know how to do it. All i did was look at ports setting USE_GROFF, triage them, and improve mandoc(1) to handle them. It is true that naddy helped a great deal with that. That said, i have heard rumours that sthen@ can run things over all manual pages in ports but i'm not quite sure, and i have no idea how he does it. If there is an easy way to get a tarball of all ports manual pages (no matter whether for -current, -release, or both), putting that up would be trivial and not cause significant additional work. I'm simply not aware of an easy way to get that tarball. Yours, Ingo
