1 |
Hello friends, |
2 |
|
3 |
On Sunday, October 29, 2017, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
4 |
> On 29/10/2017 11:11, Peter Humphrey wrote: |
5 |
>> On Sun, 29 Oct 2017 19:31:46 +1100 |
6 |
>> Adam Carter <adamcarter3@×××××.com> wrote: |
7 |
>> |
8 |
>>>> On my amd64 arch machine I; |
9 |
>>>> emerged python 3.5 |
10 |
>>>> eselected python 3.5 |
11 |
>>>> edited make.conf to set PYTHON_TARGETS to "python2_7 python3_5" |
12 |
>>>> running emerge -pv --depclean =python-3.4.5 to see what needs to be |
13 |
>>>> rebuilt Then tryed to rebuild those packages to allow removal of 3.4, |
14 |
>>>> however, it looks like that I would then have to change |
15 |
>>>> PYTHON_SINGLE_TARGET to 3.5 too, and some other packages still require |
16 |
>>>> it to be set to 2.7, so i've bailed out of trying to get rid of 3.4 on |
17 |
>>>> that box. I'll leave PYTHON_TARGETS at "python2_7 python3_5" unless I |
18 |
>>>> find something that also needs 3.4 in there. |
19 |
>>>> |
20 |
>>>> Failure came fast, example; |
21 |
>>> The following REQUIRED_USE flag constraints are unsatisfied: |
22 |
>>> python? ( at-most-one-of ( python_targets_python3_4 |
23 |
>>> python_targets_python3_5 python_targets_python3_6 ) |
24 |
>>> |
25 |
>>> So ive unset PYTHON_TARGETS and PYTHON_SINGLE_TARGET again. |
26 |
>> |
27 |
>> Do you actually need any python entries in make.conf? I'm running happily |
28 |
>> here without any. I just let the profile and ebuilds sort out what they |
29 |
>> need. |
30 |
>> |
31 |
> |
32 |
> |
33 |
> For the most part, and for the regular user, that is generally fine. The |
34 |
> devs and profile maintainers take care of all the fiddly bits and ensure |
35 |
> that the settings are correct across the tree when they update the |
36 |
> profile to use the next Pythn version |
37 |
> |
38 |
> For some users (aka the typical Gentoo'er) that doesn't really cut it. |
39 |
> Maybe the user wants to fiddle with python-3.5 before the profile is |
40 |
> ready for it. |
41 |
> |
42 |
> Maybe the user wants to use some nifty new package or take advantage of |
43 |
> new features in python-3.5. This is the thing R0b0t1 was referring to. |
44 |
> In that case, the user must do for himself what the profile maintainers |
45 |
> do for you. That user also gets to keep all the shiny broken bits whilst |
46 |
> figuring out what to set for what |
47 |
> |
48 |
|
49 |
I've mentioned this on the forum, but unless a user is interested in |
50 |
specifically testing Python's interaction with system packages it is |
51 |
probably best to merge new versions explicitly. There will be lots of shiny |
52 |
pieces indeed. |
53 |
|
54 |
Cheers, |
55 |
R0b0t1. |