| 1 |
On Sun, Jan 24, 2021 at 7:21 AM Michał Górny <mgorny@g.o> wrote: |
| 2 |
> |
| 3 |
> For this reason, we have decided to change the default python-exec |
| 4 |
> configuration to match PYTHON_TARGETS by default, in the eclass |
| 5 |
> preference order, that is from the newest CPython version to oldest, |
| 6 |
> with alternative Python implementations coming afterwards. This change |
| 7 |
> will be propagated via the configuration protection mechanism whenever |
| 8 |
> dev-lang/python-exec-conf is installed or rebuilt due to PYTHON_TARGETS |
| 9 |
> changes. This will permit the users to interactively confirm |
| 10 |
> the updates. |
| 11 |
> |
| 12 |
> If the new default is not correct for you, please use your preferred |
| 13 |
> configuration update tool to discard or edit the new configuration file. |
| 14 |
|
| 15 |
Could we just spell out what the actual setting is? That way if a |
| 16 |
user accepts or rejects the change accidentally it is trivial to fix, |
| 17 |
vs making them hunt through the installed files to do a diff... |
| 18 |
|
| 19 |
Nothing wrong with the instructions - I'd just add one line about what |
| 20 |
setting controls this. |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives