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.
>
OK, I'm looking at this based on DJ's comment. The second part is
unterminated, but is that not changing deliberate invocations of
python2 to python3 ? That sounds like a very bad idea (e.g. the
sort of thing which would break qtwebengine if it was applied
there). Using the first part in a fresh build to confirm some
details about altering _my_ build to match the book (I was building
docs after the install).
ĸen
--
The people next door oppress me all night long. I tell them: I work
all day, a man's got to have some time to learn to play the tuba.
That's oppression, that is. [ Guards! Guards! ]
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
