1 |
On Sun, 29 Oct 2017 19:31:46 +1100 |
2 |
Adam Carter <adamcarter3@×××××.com> wrote: |
3 |
|
4 |
> > On my amd64 arch machine I; |
5 |
> > emerged python 3.5 |
6 |
> > eselected python 3.5 |
7 |
> > edited make.conf to set PYTHON_TARGETS to "python2_7 python3_5" |
8 |
> > running emerge -pv --depclean =python-3.4.5 to see what needs to be |
9 |
> > rebuilt Then tryed to rebuild those packages to allow removal of 3.4, |
10 |
> > however, it looks like that I would then have to change |
11 |
> > PYTHON_SINGLE_TARGET to 3.5 too, and some other packages still require |
12 |
> > it to be set to 2.7, so i've bailed out of trying to get rid of 3.4 on |
13 |
> > that box. I'll leave PYTHON_TARGETS at "python2_7 python3_5" unless I |
14 |
> > find something that also needs 3.4 in there. |
15 |
> > |
16 |
> > Failure came fast, example; |
17 |
> The following REQUIRED_USE flag constraints are unsatisfied: |
18 |
> python? ( at-most-one-of ( python_targets_python3_4 |
19 |
> python_targets_python3_5 python_targets_python3_6 ) |
20 |
> |
21 |
> So ive unset PYTHON_TARGETS and PYTHON_SINGLE_TARGET again. |
22 |
|
23 |
Do you actually need any python entries in make.conf? I'm running happily |
24 |
here without any. I just let the profile and ebuilds sort out what they |
25 |
need. |
26 |
|
27 |
-- |
28 |
Regards, |
29 |
Peter. |