Page MenuHomeFreeBSD

bsd.man.mk: add MANGROUPS
ClosedPublic

Authored by ivy on Jul 24 2025, 3:52 PM.
Tags
None
Referenced Files
F131696272: D51490.id159021.diff
Fri, Oct 10, 10:26 AM
F131696270: D51490.id159006.diff
Fri, Oct 10, 10:26 AM
F131696269: D51490.id.diff
Fri, Oct 10, 10:26 AM
F131696268: D51490.id159107.diff
Fri, Oct 10, 10:26 AM
F131696255: D51490.diff
Fri, Oct 10, 10:25 AM
Unknown Object (File)
Fri, Oct 3, 9:00 AM
Unknown Object (File)
Fri, Oct 3, 3:59 AM
Unknown Object (File)
Thu, Oct 2, 9:49 PM

Details

Summary

MANGROUPS allows manpages to be divided into groups with their own
options, analogous to CONFGROUPS. This is mainly used for installing
manpages into the correct package by setting ${<group>PACKAGE}.

Convert the backward-compatibility variables MAN1..MAN8 into man
groups.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 65669
Build 62552: arc lint + arc unit

Event Timeline

ivy requested review of this revision.Jul 24 2025, 3:52 PM
share/mk/bsd.man.mk
219

This logic is premised on MAN containing things like cat.1 foo.8 etc, is that going to also be true for MANGROUPS in general?

share/mk/bsd.man.mk
219

yes, it should be. essentially where before you did this:

MAN= foo.1 bar.1

now you could do this:

MANGROUPS= FOO BAR
FOO=foo.1
BAR=bar.1

so ${${__group}} -> ${FOO} -> foo.1 should be semantically equivalent to ${MAN} -> foo.1.

fix ${PACKAGE} + ${MLINKS}

discovered during testing that this didn't work properly:

PACKAGE=kernel-man
MLINKS=foo.1 bar.1

the links would be installed in the utilities-man package because the
manlinksinstall target wasn't using the group-specific TAG_ARGS.

now it works.

This revision is now accepted and ready to land.Jul 24 2025, 7:09 PM
This revision was automatically updated to reflect the committed changes.