On 10/23/20 11:01 AM, Ken Moffat via blfs-dev wrote:
On Fri, Oct 23, 2020 at 10:27:51AM -0500, DJ Lucas via blfs-dev wrote:
On October 23, 2020 10:15:09 AM CDT, Ken Moffat via blfs-dev
<blfs-dev@lists.linuxfromscratch.org> wrote:
On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev
wrote:
Reluctantly, I have to go with a python symlink. Out of the more
than 48000 tests in clang-11.0, one uses /usr/bin/env/python.
When we find something like that, couldn't we use:
grep -rl '#!.*python' | xargs sed -i
'1{s/python$/python3/;s/python[^3]/python3}'
or so?
Of course, P2 only scripts would still fail, but at least, nothing
would depend on a python symlink.
Pierre
I think the problem is more that using env python is hidden deep
within a lot of packages.
This _should_ go away on its own eventually. You are supposed to specify the
major version. If a particular script doesn't, it is broken. Opening bugs for
these errors upstream is entirely appropriate.
--DJ
Is there an official python recommendation for that, to quote at
them, please ?
That's a good question, but I would also like to see if there is a
survey of the major distros on the subject. I know arch has had
python->python3 for a long time, but I don't know what Debian, Gentoo,
Fedora, SUSe, Slackware, etc currently do. Does anyone know or have
access to systems that can easily check?
In the past most had python->python2 because that was baked into the p2
Makefile. Creating a symlink is not in the current p3 Makefile.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
