From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Russ Allbery <rra@debian.org>
Cc: Alejandro Colomar <alx@kernel.org>,
debian-policy@lists.debian.org,
"Dr. Tobias Quathamer" <toddy@debian.org>,
linux-man@vger.kernel.org,
Helge Kreutzmann <debian@helgefjell.de>,
Colin Watson <cjwatson@debian.org>
Subject: Re: Stop compressing manual pages
Date: Thu, 25 Dec 2025 21:08:11 -0600 [thread overview]
Message-ID: <20251226030811.6pwpbmgp434l6pd5@illithid> (raw)
In-Reply-To: <87ms364c05.fsf@hope.eyrie.org>
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
At 2025-12-25T11:06:34-0800, Russ Allbery wrote:
> > Yup, I'd like that policy to change. I've added debian-policy@ to
> > this mail (and also linux-man@).
>
> 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.
I'd add that, in contrast to the mid-1990s when Debian's man page
compression policy was promulgated--my recollection is that it was an
early, early decision, already in place when I started using Debian in
January 1996--transparent compression is now an oft-implemented feature
of file systems, including some that are popular in embedded systems,
such as JFFS2, where it's been the case for at least 19 years.[1]
Further, the selection of compression algorithm and container format has
become a popular site for partisan battles over the same.[2][3][4][5][6]
Since Debian already generates sufficient partisan battles over issues
specific to our practices, it might be advantageous to abandon this one.
(Speaking for myself, I find deflate/gzip satisfactory, and I intend to
release groff 1.24.0 as a gzipped tape archive.)
Adopting this change would enable man-db man(1) to discard the
zsoelim(1) tool, simplifying the code base and logic depending on this
tool--but I defer to Colin's judgment of how advantageous that'd be.
Regards,
Branden
[1] https://lwn.net/Articles/219827/
[2] https://linuxreviews.org/Comparison_of_Compression_Algorithms
[3] https://www.nongnu.org/lzip/xz_inadequate.html
[4] https://engineering.fb.com/2016/08/31/core-infra/smaller-and-faster-data-compression-with-zstandard/
[5] https://www.reddit.com/r/archlinux/comments/eiia99/zst_packages_consistently_larger_than_xz/
[6] https://sysdfree.wordpress.com/2020/01/04/293/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-26 3:08 UTC|newest]
Thread overview: 8+ 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 ` Stop compressing manual pages Russ Allbery
2025-12-26 3:08 ` G. Branden Robinson [this message]
2025-12-26 10:51 ` Marc Haber
2025-12-26 14:52 ` Simon McVittie
2026-04-19 6:51 ` Alejandro Colomar
2026-04-20 10:14 ` Colin Watson
2026-05-09 19:42 ` Alejandro Colomar
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=20251226030811.6pwpbmgp434l6pd5@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=cjwatson@debian.org \
--cc=debian-policy@lists.debian.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=rra@debian.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