public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@gentoo.org>
Subject: AW: [gentoo-dev] Gzipped HTML docs in /usr/share/doc
Date: Tue, 19 Feb 2002 09:57:03 +0100	[thread overview]
Message-ID: <000501c1b923$67cee210$be01a8c0@KISSWebMedias> (raw)
In-Reply-To: <1014105867.7048.24.camel@lipari.mdy.univie.ac.at>

You are right. Leave all directories which contains html-documentation
without compression or put all files in one tar file and compress this
file.

Greetings

Sebastian

-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org] Im
Auftrag von Stefan Boresch
Gesendet: Dienstag, 19. Februar 2002 09:04
An: gentoo-dev@gentoo.org
Betreff: [gentoo-dev] Gzipped HTML docs in /usr/share/doc

I have recently stumbled across a lot of gzipped *.html *.htm
files in the /usr/share/doc hierarchy.  I don't like it very much
since this breaks all navigation links.  My question is: is this
intended, should I write bug reports, should I submit patches (provided
I figure out who is the 'culprit' for the compression (I suppose this is
a 'feature' of ebuild at some level)

Thanks,

Stefan Boresch

PS: Assuming that the compression of documentation is done
semi-automatically by ebuild, might it not be the easiest to either
exclude htm(l) pages from compression, or make the behavior user
controllable...?




_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2002-02-19  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19  8:04 [gentoo-dev] Gzipped HTML docs in /usr/share/doc Stefan Boresch
2002-02-19  8:57 ` Sebastian Werner [this message]
2002-02-20 16:41   ` Chris Houser
  -- strict thread matches above, loose matches on Subject: below --
2002-02-20  0:16 AW: " Stefan Boresch
2002-02-20  4:02 ` Arcady Genkin

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='000501c1b923$67cee210$be01a8c0@KISSWebMedias' \
    --to=sebastian@werner-productions.de \
    --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