From: Russ Allbery <rra@debian.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: debian-policy@lists.debian.org,
"Dr. Tobias Quathamer" <toddy@debian.org>,
linux-man@vger.kernel.org,
Helge Kreutzmann <debian@helgefjell.de>,
"G. Branden Robinson" <branden@debian.org>,
Colin Watson <cjwatson@debian.org>
Subject: Re: Stop compressing manual pages
Date: Thu, 25 Dec 2025 11:06:34 -0800 [thread overview]
Message-ID: <87ms364c05.fsf@hope.eyrie.org> (raw)
In-Reply-To: <aU1D0aL00gy1V-NX@devuan> (Alejandro Colomar's message of "Thu, 25 Dec 2025 15:15:03 +0100")
Alejandro Colomar <alx@kernel.org> writes:
> On Thu, Dec 25, 2025 at 02:47:33PM +0100, Dr. Tobias Quathamer wrote:
>> Am 25.12.25 um 12:20 schrieb Alejandro Colomar:
>>> Indeed, compressed manual pages are a pain to work with. You can't use
>>> regular Unix tools to work with them. With uncompressed manual pages,
>>> You can go to /usr/share/man, and run a pipe of programs to do a complex
>>> search. With tools like zgrep(1) and zcat(1), you can do some stuff,
>>> but not everything.
[...]
>> thanks for your bug report and the provided statistics. I haven't thought
>> about this up until now, because it violates Debian Policy. Quoting from
>> Section 12.1
>> (https://www.debian.org/doc/debian-policy/ch-docs.html#manual-pages):
>>
>> "Manual pages should be installed compressed using gzip -9."
[...]
> Yup, I'd like that policy to change. I've added debian-policy@ to this
> mail (and also linux-man@).
Colin, do you have an opinion on this as the man-db maintainer? The
software you maintain is probably the primary consumer by a significant
margin of the installed manual pages.
The rationale in Debian for compressing documentation in general is for
embedded systems and other small installations, and it applies to just
about anything that can be safely compressed (manual pages are only one
example). But this rule also predates such facilities as the nodoc build
profile, and is several decades old and thus predates the growth in
storage size even in small embedded environments that has significantly
outpaced the size of text-adjacent documents. I would definitely want to
get feedback from embedded folks before changing this rule, but at least
at first glance it sounds like a reasonable request worth considering.
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2025-12-25 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aUzUvdZEJpDHb3QX@meinfjell.helgefjelltest.de>
[not found] ` <aU0WjfHED1esOwPy@devuan>
[not found] ` <fec615b5-af5b-46cd-ae09-d9343db6da77@debian.org>
2025-12-25 14:15 ` Stop compressing manual pages (was: Bug#1123959: manpages: Please consider shipping uncompressed man pages) Alejandro Colomar
2025-12-25 19:06 ` Russ Allbery [this message]
2025-12-26 3:08 ` Stop compressing manual pages G. Branden Robinson
2025-12-26 10:51 ` Marc Haber
2025-12-26 14:52 ` Simon McVittie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ms364c05.fsf@hope.eyrie.org \
--to=rra@debian.org \
--cc=alx@kernel.org \
--cc=branden@debian.org \
--cc=cjwatson@debian.org \
--cc=debian-policy@lists.debian.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=toddy@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).