Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Colin Watson <cjwatson@debian.org>, Russ Allbery <rra@debian.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>
Subject: Re: Stop compressing manual pages
Date: Sun, 19 Apr 2026 08:51:03 +0200	[thread overview]
Message-ID: <aeR7MzmSQHRHLK2q@devuan> (raw)
In-Reply-To: <87ms364c05.fsf@hope.eyrie.org>

[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]

Hi Colin,

On 2025-12-25T11:06:34-0800, Russ Allbery wrote:
> 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.

Ping.


Have a lovely day!
Alex

> 
> 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/>

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-04-19  6:51 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
2025-12-26 10:51         ` Marc Haber
2025-12-26 14:52           ` Simon McVittie
2026-04-19  6:51         ` Alejandro Colomar [this message]
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=aeR7MzmSQHRHLK2q@devuan \
    --to=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=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