1 |
On Mon, 13 Apr 2015 07:48:25 +0200 |
2 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
3 |
|
4 |
> On 13/04/2015 03:07, »Q« wrote: |
5 |
> > On Sun, 12 Apr 2015 21:35:07 +0300 |
6 |
> > Matti Nykyri <matti.nykyri@×××.fi> wrote: |
7 |
> > |
8 |
> >>> On Apr 12, 2015, at 20:23, »Q« <boxcars@×××.net> wrote: |
9 |
> >>> |
10 |
> >>> On Sun, 12 Apr 2015 11:12:38 +0200 |
11 |
> >>> "J. Roeleveld" <joost@××××××××.org> wrote: |
12 |
> >>> |
13 |
> >>>> On Saturday, April 11, 2015 08:42:20 PM Alan Grimes wrote: |
14 |
> >>> |
15 |
> >>>>> PYTHON_TARGETS="${PYTHON_TARGETS} python2_7 python3_4" |
16 |
> >>>>> PYTHON_SINGLE_TARGET="python2_7" |
17 |
> >>>> |
18 |
> >>>> These are set in your profile, please do not override this. |
19 |
> >>>> In other words, please remove these 2 lines. |
20 |
> >>> |
21 |
> >>> I'm not the OP. (I spend less time than him on maintaining my |
22 |
> >>> system.) |
23 |
> >>> |
24 |
> >>> Should those variables really not be set in make.conf? I added |
25 |
> >>> them to make.conf some time back because portage complained about |
26 |
> >>> them, and if I comment them out, it complains again, like so: |
27 |
> > |
28 |
> >>> The following REQUIRED_USE flag constraints are unsatisfied: |
29 |
> >>> python? ( exactly-one-of ( python_single_target_python3_3 |
30 |
> >>> python_single_target_python3_4 python_single_target_python2_7 ) ) |
31 |
> > |
32 |
> > [snip] |
33 |
> > |
34 |
> >> This is because you have set the "python" use flag in your |
35 |
> >> make.conf (or package.use). |
36 |
> >> |
37 |
> >> Remove the python useflag and the problem goes away. It is not set |
38 |
> >> by the profile but by you. Do you really need it? |
39 |
> > |
40 |
> > I enabled it globally (in make.conf), but I think I only need it |
41 |
> > for one or two packages. If I remove it from USE, I get portage |
42 |
> > complaining about other things. |
43 |
> |
44 |
> |
45 |
> USE="python" is one of those flags that has no accurate meaning in |
46 |
> real life, and the user needs to make an informed decision. It |
47 |
> doesn't work like USE="sse" for example, which means packages that |
48 |
> can use the sse instruction set will compile for it. It's a fairly |
49 |
> exact meaning. |
50 |
> |
51 |
> USE="python" means "use python to do stuff" but stuff is not defined |
52 |
> and it's usually hard to find out what it is for a given package. For |
53 |
> some it means to build optional extra tools that run under python, |
54 |
> for some it means to create python language bindings, and for others |
55 |
> it could even mean some critical system function that is implemented |
56 |
> in python and eats your kittens if not enabled. (sort of like how |
57 |
> portage is implemented in python; there's no USE for it but you get |
58 |
> the idea). |
59 |
> |
60 |
> Usually, USE="python" should be set per-package if you need what it |
61 |
> does. I had it in make.conf myself in my early days and kept getting |
62 |
> into circular dependencies. Sorting that out took some effort. |
63 |
> |
64 |
> Portage will almost certainly complain if you take something with |
65 |
> far-reaching effects as USE="python" in make.conf and remove it. |
66 |
> |
67 |
> So, take each thing it is complaining about and enable or disable it |
68 |
> based on what you need. Tweak as necessary to get the result you want. |
69 |
|
70 |
Thanks -- that all makes sense. I'm pretty sure I have USE="python" |
71 |
because I thought something like "I'm going to have python, so I might |
72 |
as well let things use it", which I now see to be muddle-headed at |
73 |
best. |
74 |
|
75 |
Since it's not causing me any troubles for now, I'll wean myself off of |
76 |
USE="python" when there's some in which I can afford to fix whatever I |
77 |
break during the process. |