man-db 2.7.0
Milestone information
- Active:
- Yes. Drivers can 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
Upgrading from previous versions:
-------
For the first time since version 2.4.0, the database format has
changed slightly, so you will need to run 'mandb --create' after
installing the new version to rebuild your databases from scratch.
(Distribution packages should do this automatically for system
databases.)
Fixes:
------
o lexgrog now filters terminal escape sequences out of cat pages
before trying to parse them.
o Tools that consider the terminal line length now prioritise the
COLUMNS environment variable above the TIOCGWINSZ ioctl.
o Manpath elements are no longer canonicalised before being inserted
into the search path; this caused the use of incorrect catpaths in
some cases. This was broken by the LANGUAGE-handling fixes in
2.5.4.
Improvements:
-------------
o Ship a systemd tmpfiles snippet to clean up old cat files after a
week.
o The modification time of manual databases is now simply stored in
the mtime of the database files themselves, rather than using a
special row. This makes databases reproducible between
otherwise-
database has predictable behaviour. As a bonus, man-db now uses
high-precision timestamps to determine whether it needs to update
databases.
o Timestamps of manual pages are also now stored in the database
with high precision and compared accordingly.
o Files are now ordered by first physical extent before reading
them, for substantial performance improvements in operations such
as mandb and 'man -K'.
o 'man -H' shows a better error message if no browser is configured.
o zsoelim is now installed in $pkglibexecdir, to avoid clashes with
other packages.
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.