On Wed, Jan 30, 2019 at 04:35:29PM -0000, BLFS Trac wrote:
> #11549: Review dependencies on Python 2
>
> Comment (by pierre.labastie):
>
> So I've been able to build KF5, plasma, and KF5 applications without P2.
> At some point, I needed asciidoc (recommended for btrfs-progs, which is
> itself recommendend for udisks2, which is needed at runtime by KDE
> applications). So:
>
> - I installed P2
> - I moved /usr/bin/{python,python2,python2.7} to
> /usr/bin/{python,python2,python2.7}nouse
> - I changed the headers of a2x and asciidoc from /usr/bin/python to
> /usr/bin/python2.7nouse
>
> asciidoc is now working, but P2 is invisible to any other package... I
> wonder if we could not use this kind of approach in the book, for packages
> which need P2 at run time.
>
One of the packages whose *users* use python2 at runtime is gimp.
There are many python2 scripts out there (non-programmers find it
easier to adapt py scripts than scheme scripts). They are probably
all external, and using /usr/bin/env python (or ...2 or ...2.7).
ĸen
--
thread 'main' panicked at 'giraffe',
/tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
