| 1 |
On Thu, May 19, 2011 at 02:40:01AM +0200, Dale wrote: |
| 2 |
> I have a quick question. I sync'd a bit ago and noticed something a bit |
| 3 |
> odd. Here it is: |
| 4 |
> |
| 5 |
> [ebuild U *] sys-apps/portage-2.2.0_alpha34 [2.2.0_alpha33] |
| 6 |
> USE="(ipc) -build -doc -epydoc -python2 -python3 (-selinux)" |
| 7 |
> LINGUAS="-pl" 794 kB |
| 8 |
> |
| 9 |
> I know portage needs python but check out the USE flags. Both python2 |
| 10 |
> and python3 are disabled. Shouldn't one of those be enabled? Even |
| 11 |
> better, shouldn't portage complain a bit about this before emerging? |
| 12 |
> Thing is, I'm tempted to enable them both. 2.7 is currently being used |
| 13 |
> but won't 3.1 be used eventually? Should I enable both or just emerge as |
| 14 |
> is? |
| 15 |
> |
| 16 |
|
| 17 |
Pretty sure that if you have -python2 or whatever that only works |
| 18 |
against building things which have an optional python bit, and has no |
| 19 |
effect on things you have which are python-based system bits. |
| 20 |
The USE flags affect options, they don't bar things altogether. |
| 21 |
I have "-gtk -qt4 -qt3support" in make.conf, but it doesn't stop me |
| 22 |
from installing gtk-based things -- just stops the building of |
| 23 |
*optional* gtk guis. |
| 24 |
|
| 25 |
Even so, I wouldn't do that with something as critical as python. |
| 26 |
|
| 27 |
The real question is "why do you hate python"? |
| 28 |
:) |
| 29 |
|
| 30 |
-- |
| 31 |
caveat utilitor |
| 32 |
♫ ❤ ♫ ❤ ♫ ❤ ♫ |
Archives