From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!]
Date: Mon, 25 Apr 2011 08:49:35 +0100 [thread overview]
Message-ID: <201104250849.54534.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20110425083058.127bdab8@digimed.co.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1056 bytes --]
On Monday 25 April 2011 08:30:58 Neil Bothwick wrote:
> On Sun, 24 Apr 2011 23:16:39 +0100, Mick wrote:
> > > It's rarely desirable to enable doc globally. It is best to enable
> > > only for those packages where you need extended documentation.
> >
> > @Alan Mackenzie:
> >
> > What Neil is saying can be achieved by setting package specific USE
>
> > flags in the file /etc/portage/package.use; e.g. use an entry like:
> What I'm saying is that you should have -doc in /etc/make.conf and enable
> it on a per-package basis. The doc flag builds extra documentation that
> general users don't need, man/info/html pages are included by default (at
> least, that's how it is supposed to work, the odd package, like ffmpeg,
> won't even include a man page without the doc flag).
The doc USE flag is disabled by default on my make.profile
(amd64/10.0/desktop), so although it won't need to be set as -doc in
/etc/make.conf, it will need to be set as doc in the packages that need it in
/etc/portage/package.use.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-25 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gKx1n-6tR-7@gated-at.bofh.it>
[not found] ` <gL2RA-GN-11@gated-at.bofh.it>
[not found] ` <gL7Rg-uS-7@gated-at.bofh.it>
[not found] ` <gL9Jo-3CO-19@gated-at.bofh.it>
[not found] ` <gLdjY-1dS-15@gated-at.bofh.it>
2011-04-24 20:17 ` [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!] David W Noon
2011-04-24 20:30 ` Neil Bothwick
2011-04-24 22:16 ` Mick
2011-04-25 7:30 ` Neil Bothwick
2011-04-25 7:49 ` Mick [this message]
2011-04-25 10:07 ` Neil Bothwick
2011-04-25 12:02 ` Alan Mackenzie
2011-04-25 12:18 ` Stroller
2011-04-25 14:09 ` Neil Bothwick
2011-04-22 18:05 [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please! Alan Mackenzie
2011-04-23 19:46 ` Mick
2011-04-23 20:06 ` Alan Mackenzie
2011-04-24 8:17 ` Mick
2011-04-24 13:25 ` [gentoo-user] Reinstall Gentoo? [Was: Building pygtk-2.22.0-r1 fails. Help, please!] Alan Mackenzie
2011-04-24 15:44 ` Mick
2011-04-24 15:48 ` Mick
2011-04-24 17:17 ` Stroller
2011-04-25 12:11 ` Alan Mackenzie
2011-04-25 14:12 ` Mick
2011-04-25 15:03 ` Alan Mackenzie
2011-04-25 15:29 ` Mark Knecht
2011-04-26 19:43 ` Alan Mackenzie
2011-04-25 16:00 ` Mick
2011-04-26 20:05 ` Alan Mackenzie
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=201104250849.54534.michaelkintzios@gmail.com \
--to=michaelkintzios@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