From: Stefan Boresch <stefan@mdy.univie.ac.at>
To: gentoo-dev@gentoo.org
Subject: Re: AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc
Date: 20 Feb 2002 01:16:00 +0100 [thread overview]
Message-ID: <1014164160.1976.1.camel@lipari.mdy.univie.ac.at> (raw)
Thanks for the answer!
On Tue, 2002-02-19 at 09:57, Sebastian Werner wrote:
> You are right. Leave all directories which contains html-documentation
> without compression or put all files in one tar file and compress this
> file.
Nevertheless, what am I supposed to do? Write (a) bug report(s) (submit
patches) for each package with gzipped HTML docs I run across --- there
seem to be a lot... Or, and this makes this a more general question,
can/could this be handled on the portage/ebuild level? (I am still
at portage 1.8.8)
I guess I'am expecting (hoping for) some response from
management. Let me know whether to shut up, swamp bugs.gentoo.org
or to look into modifying ebuild (the latter may turn out problematic,
as my programming experience is rather limited...)
Cheers,
Stefan
next reply other threads:[~2002-02-20 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 0:16 Stefan Boresch [this message]
2002-02-20 4:02 ` AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc Arcady Genkin
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 8:04 Stefan Boresch
2002-02-19 8:57 ` AW: " Sebastian Werner
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=1014164160.1976.1.camel@lipari.mdy.univie.ac.at \
--to=stefan@mdy.univie.ac.at \
--cc=gentoo-dev@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