man-db 2.6.4
This release fixes build errors with Automake 1.13.
man-db 2.6.0 arranged to search the full manpath when expanding .so
directives in manual pages (so that ".so name.1" works as well as ".so
man1/name.1"), but this incorrectly did not take effect for manual pages
that consist only of a .so directive. This is now fixed. Thanks to
Peter Schiffer.
The MANLESS environment variable is now treated as if it were a default
value for the -r option to man: occurrences of the text "$MAN_PN" are
expanded, and explicitly using the -r option overrides the default.
MANPATH entries now undergo glob(7)-style wildcard expansion, allowing
entries such as "/opt/*/man". Thanks to Peter Schiffer.
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
Fixes:
------
o man(1) and catman(8) now document the default section list set at
configure time.
o Build fixes for Automake 1.13.
o man-db 2.6.0 arranged to search the full manpath when expanding
.so directives in manual pages (so that ".so name.1" works as well
as ".so man1/name.1"), but this incorrectly did not take effect
for manual pages that consist only of a .so directive. This is
now fixed.
Improvements:
-------------
o The MANLESS environment variable is now treated as if it were a
default value for the -r option to man: occurrences of the text
"$MAN_PN" are expanded, and explicitly using the -r option
overrides the default.
o The (unfortunately still hardcoded) maximum length for paths to
manual page hierarchies in the configuration file is now 511
characters rather than 49.
o MANPATH entries now undergo glob(7)-style wildcard expansion,
allowing entries such as "/opt/*/man".
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.
