| 1 |
On Sat, Dec 12, 2020 at 04:25:48PM -0500, Mike Gilbert wrote: |
| 2 |
> On Sat, Dec 12, 2020 at 3:48 PM William Hubbs <williamh@g.o> wrote: |
| 3 |
> > If both /usr/bin/python and /usr/bin/python3 are going away, the best |
| 4 |
> > choice would be to add functionality to python-exec or eselect python to tell us |
| 5 |
> > the path to the default python interpretor. Once we know that we call it |
| 6 |
> > directly. |
| 7 |
> |
| 8 |
> I don't think they are "going away". There is a USE flag on |
| 9 |
> dev-lang/python-exec that makes them optional, and I think it will be |
| 10 |
> forcibly enabled for the foreseeable future. |
| 11 |
> |
| 12 |
> > Please do not apply this patch to meson; I think we can figure something |
| 13 |
> > out that is better. |
| 14 |
> |
| 15 |
> I think installing a small script to help translate arguments from one |
| 16 |
> format to another is a reasonable solution. |
| 17 |
|
| 18 |
I think we should look at the eclass to see if we can provide functions |
| 19 |
that can be used by consumers to handle this. |
| 20 |
|
| 21 |
Also, I don't think your script will run if native-symlinks is disabled since in |
| 22 |
that setting /usr/bin/python would not exist. |
| 23 |
|
| 24 |
I question the value of the native-symlinks use flag on python-exec |
| 25 |
unless there is a way to query the path of the default python |
| 26 |
interpretor. |
| 27 |
|
| 28 |
William |
Archives