1 |
On Sun, Jan 24, 2021 at 2:09 PM Michał Górny <mgorny@g.o> wrote: |
2 |
> |
3 |
> On Sun, 2021-01-24 at 13:53 -0500, Rich Freeman wrote: |
4 |
> > On Sun, Jan 24, 2021 at 7:21 AM Michał Górny <mgorny@g.o> wrote: |
5 |
> > > |
6 |
> > > For this reason, we have decided to change the default python-exec |
7 |
> > > configuration to match PYTHON_TARGETS by default, in the eclass |
8 |
> > > preference order, that is from the newest CPython version to oldest, |
9 |
> > > with alternative Python implementations coming afterwards. This change |
10 |
> > > will be propagated via the configuration protection mechanism whenever |
11 |
> > > dev-lang/python-exec-conf is installed or rebuilt due to PYTHON_TARGETS |
12 |
> > > changes. This will permit the users to interactively confirm |
13 |
> > > the updates. |
14 |
> > > |
15 |
> > > If the new default is not correct for you, please use your preferred |
16 |
> > > configuration update tool to discard or edit the new configuration file. |
17 |
> > |
18 |
> > Could we just spell out what the actual setting is? That way if a |
19 |
> > user accepts or rejects the change accidentally it is trivial to fix, |
20 |
> > vs making them hunt through the installed files to do a diff... |
21 |
> > |
22 |
> > Nothing wrong with the instructions - I'd just add one line about what |
23 |
> > setting controls this. |
24 |
> > |
25 |
> |
26 |
> The exact paths are provided in the second paragraph. Am I missing |
27 |
> something? |
28 |
> |
29 |
|
30 |
No - the way this works makes sense now. For some reason I missed it |
31 |
on the first two reads, which makes me suspect others will as well. |
32 |
It wasn't the location of the config file I missed, but the fact that |
33 |
the eclass will just do what eselect python used to do, and thus |
34 |
trigger config protection (which is at the end of paragraph 4). |
35 |
|
36 |
For some reason when I read the section about discarding the changes I |
37 |
was thinking that there was some config toggle to change this behavior |
38 |
vs the old way things worked. Instead the new behavior is |
39 |
unconditional, but the updates it makes to the python-exec config can |
40 |
be rejected. |
41 |
|
42 |
-- |
43 |
Rich |