From: Indi <thebeelzebubtrigger@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage python USE flags.
Date: Wed, 18 May 2011 20:48:44 -0400 [thread overview]
Message-ID: <20110519004844.GA26373@gaurahari.merseine.nu> (raw)
In-Reply-To: <gTZrr-412-3@gated-at.bofh.it>
On Thu, May 19, 2011 at 02:40:01AM +0200, Dale wrote:
> I have a quick question. I sync'd a bit ago and noticed something a bit
> odd. Here it is:
>
> [ebuild U *] sys-apps/portage-2.2.0_alpha34 [2.2.0_alpha33]
> USE="(ipc) -build -doc -epydoc -python2 -python3 (-selinux)"
> LINGUAS="-pl" 794 kB
>
> I know portage needs python but check out the USE flags. Both python2
> and python3 are disabled. Shouldn't one of those be enabled? Even
> better, shouldn't portage complain a bit about this before emerging?
> Thing is, I'm tempted to enable them both. 2.7 is currently being used
> but won't 3.1 be used eventually? Should I enable both or just emerge as
> is?
>
Pretty sure that if you have -python2 or whatever that only works
against building things which have an optional python bit, and has no
effect on things you have which are python-based system bits.
The USE flags affect options, they don't bar things altogether.
I have "-gtk -qt4 -qt3support" in make.conf, but it doesn't stop me
from installing gtk-based things -- just stops the building of
*optional* gtk guis.
Even so, I wouldn't do that with something as critical as python.
The real question is "why do you hate python"?
:)
--
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫
next parent reply other threads:[~2011-05-19 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gTZrr-412-3@gated-at.bofh.it>
2011-05-19 0:48 ` Indi [this message]
2011-05-19 1:33 ` [gentoo-user] portage python USE flags Dale
2011-05-19 2:20 ` Adam Carter
2011-05-19 0:30 Dale
2011-05-19 0:58 ` Alan McKinnon
2011-05-19 1:03 ` Peter Humphrey
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=20110519004844.GA26373@gaurahari.merseine.nu \
--to=thebeelzebubtrigger@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