From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bzipped manpages
Date: Wed, 11 Jan 2017 09:20:46 -0500 [thread overview]
Message-ID: <51ed0f15-72d6-7786-0a7b-02fcf6bd4526@gentoo.org> (raw)
In-Reply-To: <20170110115421.GA4037@www.stare.cz>
On 01/10/2017 06:54 AM, Jan Stary wrote:
>
> These are workarounds. Let me get back to the original question:
> would you please consider having _uncompressed_ manpages as the default?
>
> On this particular system, the bzipped /usr/share/man/ is 67M.
> The uncompressed man/ is 108M. That's 40M saved. Seriously?
Since everyone else is giving you a hard time, I think compressing all
of the documentation by default is annoying and over-complicates things.
However, if you asked me what *could* be compressed by default, man
pages with their separate /usr/share/man directory and doman helper
would be at the top of the list. They aren't meant to be read by humans,
the default reader handles them, and they compress well.
And in direct contradiction to my last paragraph, we did invent dohtml
and now have PORTAGE_COMPRESS_EXCLUDE_SUFFIXES set to work around this
exact problem, that web browsers won't call bunzip2 in a pipeline. It
seems a little unfair to let web browsers off the hook but not mdocml.
There are probably fewer people who care about the space than there are
users who have been annoyed that they can't run an example because
ruby/php/python won't run a compressed script. I know that we have
"docompress", but inside the ebuild is the wrong place to battle an
implementation-specific default setting.
next prev parent reply other threads:[~2017-01-11 14:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 8:08 [gentoo-dev] bzipped manpages Jan Stary
2017-01-09 9:30 ` Mike Auty
2017-01-09 21:17 ` Kent Fredric
2017-01-10 11:54 ` Jan Stary
2017-01-10 11:59 ` Jan Stary
2017-01-10 12:04 ` Vadim A. Misbakh-Soloviov
2017-01-10 12:08 ` Jan Stary
2017-01-10 12:19 ` Vadim A. Misbakh-Soloviov
2017-01-10 12:36 ` Jan Stary
2017-01-11 12:34 ` Sven Eden
2017-01-11 16:15 ` Jan Stary
2017-01-13 0:08 ` Walter Dnes
2017-01-13 7:45 ` Sven Eden
2017-01-13 16:06 ` james
2017-01-17 6:05 ` Daniel Campbell
2017-01-17 14:08 ` james
[not found] ` <20170117182639.1d0eed6a.mgorny@gentoo.org>
2017-01-17 19:18 ` james
2017-01-10 13:01 ` Mart Raudsepp
2017-01-10 13:39 ` Ulrich Mueller
2017-01-10 14:02 ` Mart Raudsepp
2017-01-10 14:21 ` Michał Górny
2017-01-10 14:06 ` Michał Górny
2017-01-17 2:31 ` Kent Fredric
2017-01-11 14:20 ` Michael Orlitzky [this message]
2017-01-09 21:49 ` Jeroen Roovers
2017-01-10 12:05 ` Jan Stary
2017-01-14 12:52 ` Kent Fredric
2017-01-10 13:16 ` Fabian Groffen
2017-01-16 17:20 ` Jan Stary
2017-01-17 6:13 ` Daniel Campbell
2017-01-17 8:06 ` Fabian Groffen
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=51ed0f15-72d6-7786-0a7b-02fcf6bd4526@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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