Re: use of DOCS in port options
- In reply to: void : "Re: use of DOCS in port options"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 29 Aug 2025 09:38:36 UTC
On Thu, Aug 28, 2025 at 9:59 PM void <void@f-m.fm> wrote: > > OK, thanks. > > I guess there's not an official way of processing the ports tree to > see what's where? There's a couple of issues, might be near-edge cases, > in that on a for example embedded system one might not want doxygen > or PDFs made. I install docs-everything in a desktop context, > manpages only elsewhere. Yes, I saw such decoupling as well. For instance, if docs generation requires Doxygen, which is a pretty heavy build dep, the port does something like this: OPTIONS_DEFINE= DOCS DOXYGEN DOXYGEN_IMPLIES= DOCS DOXYGEN_BUILD_DEPENDS= doxygen:devel/doxygen DOXYGEN_CMAKE_ON= BUILD_DOCS This allows for users to disable the DOXYGEN option by default, but enable DOCS and MANPAGES, and then hope for a better port building experience. Another example of the same idea is lang/ghc with DOCS and PDFDOCS.