From: "Eric Martin" <freak4uxxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to prevent documentation in /usr/share/doc from being bzip2'ed ?
Date: Thu, 30 Oct 2008 19:39:10 -0400 [thread overview]
Message-ID: <ae47c6e50810301639m6d06c8b3qb075eb328e2c540d@mail.gmail.com> (raw)
In-Reply-To: <1225407341.31431.11.camel@blackwidow.nbk>
Why not go even easier and use bzcat,bzless,zcat,and zless
On 10/30/08, Albert Hopkins <marduk@letterboxes.org> wrote:
>
>> ,----
>> | % emerge --info libxcb
>> | Portage 2.2_rc12 (default/linux/amd64/2008.0/no-multilib, gcc-4.1.2,
>> glibc-2.6.1-r0, 2.6.25-gentoo-r7 x86_64)
> [blah]
>
>> Any ideas why PORTAGE_COMPRESS_* aren't set on my box.
>
> Because you haven't set them. Therefore they take the defaults. BTW,
> 'emerge --info' doesn't print out every portage variable, only the
> "interesting" ones (e.g. ones useful for submitting bug reports).
>
>> BtW, how do I see
>> what PORTAGE_COMPRESS_EXCLUDE_SUFFIXES is set to.
>
> # cat /etc/make.conf /etc/make.globals /etc/make.profile/make.defaults \
> |grep -m 1 ^PORTAGE_COMPRESS_EXCLUDE_SUFFIXES
>
> Also the man page for make.conf lists many common defaults.
>
>
>
next prev parent reply other threads:[~2008-10-30 23:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 13:43 [gentoo-user] How to prevent documentation in /usr/share/doc from being bzip2'ed ? Ashish Shukla आशीष शुक्ल
2008-10-30 14:01 ` Albert Hopkins
2008-10-30 14:02 ` Daniel Pielmeier
2008-10-30 22:24 ` Ashish Shukla आशीष शुक्ल
2008-10-30 22:55 ` Albert Hopkins
2008-10-30 23:39 ` Eric Martin [this message]
2008-10-31 0:12 ` Neil Bothwick
2008-10-31 0:38 ` felix
2008-10-31 5:49 ` Paul Hartman
2008-10-31 10:24 ` Neil Bothwick
2008-10-30 23:51 ` Ashish Shukla आशीष शुक्ल
2008-10-30 22:50 ` Iain Buchanan
2008-10-30 23:48 ` Ashish Shukla आशीष शुक्ल
2008-10-31 2:50 ` Iain Buchanan
2008-10-31 0:40 ` felix
2008-10-31 2:23 ` Andrey Falko
2008-10-31 5:42 ` felix
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=ae47c6e50810301639m6d06c8b3qb075eb328e2c540d@mail.gmail.com \
--to=freak4uxxx@gmail.com \
--cc=gentoo-user@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