1. Forum
  2. USENET
  3. muc.lists.freebsd.ports

  • use of DOCS in port options

    From void@void@f-m.fm to muc.lists.freebsd.ports on Thu Aug 28 19:22:10 2025
    From Newsgroup: muc.lists.freebsd.ports

    Hi,

    Can DOCS include MANPAGES?
    I'd like to build my ports with just manpages and examples.
    Does disabling DOCS globally also clobber ports manpages?
    --


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Gleb Popov@arrowd@freebsd.org to muc.lists.freebsd.ports on Thu Aug 28 21:37:21 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu, Aug 28, 2025 at 9:22rC>PM void <void@f-m.fm> wrote:

    Hi,

    Can DOCS include MANPAGES?
    I'd like to build my ports with just manpages and examples.
    Does disabling DOCS globally also clobber ports manpages?
    I'm not a portmgr, so this is all my humble opinion:
    Ideally we should strive to separate DOCS and MANPAGES. But sometimes
    the software's buildsystem has a single "docs" switch that controls
    both manpages and html/pdf/etc. generation. In this case I don't go as
    far as decoupling DOCS and MANPAGES and stick with only DOCS.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From void@void@f-m.fm to muc.lists.freebsd.ports on Thu Aug 28 19:59:03 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu, Aug 28, 2025 at 09:37:21PM +0300, Gleb Popov wrote:

    I'm not a portmgr, so this is all my humble opinion:
    Ideally we should strive to separate DOCS and MANPAGES. But sometimes
    the software's buildsystem has a single "docs" switch that controls
    both manpages and html/pdf/etc. generation. In this case I don't go as
    far as decoupling DOCS and MANPAGES and stick with only DOCS.

    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.
    --


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Gleb Popov@arrowd@freebsd.org to muc.lists.freebsd.ports on Fri Aug 29 12:34:27 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu, Aug 28, 2025 at 9:56rC>PM Derek Schrock
    <dereks@lifeofadishwasher.com> wrote:

    sub-packages solve this for all cases. You might still have to build
    them but they get their own package.
    Not really, subpackages is a way to get multiple packages from a
    single build (read, ${WRKDIR}).
    The question is about OPTIONS, which are inputs to the build (the
    build recipe actually).
    In other words, OPTIONS allows for not building some part of the
    software at all, saving the
    time on build dependencies, while subpackages allow for more
    fine-grained installation of
    build products on the end point.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Gleb Popov@arrowd@freebsd.org to muc.lists.freebsd.ports on Fri Aug 29 12:38:36 2025
    From Newsgroup: muc.lists.freebsd.ports

    On Thu, Aug 28, 2025 at 9:59rC>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.
    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2