On 9/21/19 7:46 AM, rhubarbpieguy--- via blfs-support wrote:
Although Python 3 is now installed in LFS, it appears necessary to
reinstall Python 3 in BLFS to install Python modules. From the Python
3 documentation:
"Python 3 was installed in LFS. The only reason to install it here
is if optional modules are needed."
I understand the note, but a user following dependency links doesn't
see it. For instance, Mako is required for Mesa, but the Mako link
references the Mako page, which makes no mention of reinstalling
Python 3. As Python 3 was installed in LFS, a user would have no
reason to suspect Python 3 must be reinstalled.
Would it make sense to add a note to Python modules using python3
indicating Python 3 must be reinstalled?
Is it practical to amend the Python 3 LFS procedures to eliminate
reinstalling Python 3 in BLFS? That would eliminate the need for
notes in BLFS and the Python 3 documentation.
Sadly it isn't practical to do that. We'd have to add Tk, Sqlite, and
Berkeley DB to LFS. Sqlite has 0 dependencies, but Tk requires Xorg
Libraries. I believe that the places where these modules are needed is
properly marked in BLFS, but I'm not sure. The only places where an xref
is done at is in:
general/genlib/libxml2.xml: built by <xref linkend="python3"/>, run:
general/genutils/iso-codes.xml: <xref linkend="python3"/>
I'm not sure if all of the places where those modules are used is
marked. I know I personally rebuild Python3 with the SQLite module
before GLib, but that's either due to an application I build / use or an
artifact of a previous time when Python3 wasn't part of LFS.
As Bruce said earlier, none of the Python Modules in BLFS need Python3
to be rebuilt.
- Doug
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
