Update of bug #68554 (group groff):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #2:
[comment #1 comment #1:]
> To add a perspective from a "source distro" builder (Yocto
> Project/OpenEmbedded), we are currently carrying a patch which disables the
> contrib and doc directories during the build:
>
> https://git.openembedded.org/openembedded-core/commit/?id=9deeb7474b2586eb031e4f00a644aed9ccf8cb19
>
> We cross compile and we disable those when we build the "native" tools
> variant, which is effectively our bootstrapping. I'm less concerned about
> perl and more interested in not spending resources building things we don't
> need/use.
>
> With that in mind, two configure options, --disable-contrib and
> --disable-docs would be wonderful from our perspective.
`--disable-contrib` should not be troublesome to support, and philosophically,
should be already--they're "contributed components" after all, not part of
"groff proper", though the groff developers have steadily assimilated
maintenance of most of the contrib directory's contents over the years as
original authors have drifted away.
I'm less sanguine about the idea of a `--disable-docs` build.
I think you _want_ to generate the docs as part of any build, because they can
work as acceptance tests.
https://lists.gnu.org/archive/html/groff/2026-07/msg00042.html
Do you skip "make check" as well?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68554>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
