Re: [blfs-dev] If P2 modules are built for PyYaml and Markupsafe, then recommend P2
On 10/29/20 7:23 AM, Bruce Dubbs via blfs-dev wrote: On 10/29/20 5:22 AM, Pierre Labastie via blfs-dev wrote: As the subject says... But another possibility is to not propose P2 modules at all for those packages. I'm almost sure nothing uses P2 modules for those packages: Markupsafe is here only for Mako and Jinja2, and we build only P3 for those packages. PyYAML is optional for llvm and kf5, and I think those use P3 only now... Let's drop p2 from instructions where it is not needed by something in the book. I do not see a problem with having p2 as an optional dependency though. Agreed here Looking I now see p2 instructions for D-Bus Python, PyCairo-1.18.2, PyGObject-2.28.7, libxml2-2.9.10, lxml, MarkupSafe, PyYAML, and six. However as best I can tell in the python modules section only PyCairo-1.18.2, PyGObject-2.28.7, and libxml2-2.9.10 need p2. I think lxml, MarkupSafe, and PyYAML could probably have their Python2 modules removed. I'm not sure on 'six' though. Of course the biggest problem appears to be those packages that need pygtk which uses PyGObject-2.28.7 and PyCairo-1.18.2. On top of that, I think libxml2_python is used for GIMP IIRC. On that note, I do know that the NMAP developers are working on porting Zenmap to Pygobject3 and GTK3. That should remove another PyGTK dependency. I am not sure what's going on with Avahi though. If I'm not mistaken, bssh/bvnc, which allow you to search for VNC servers and SSH servers on a network, are still using PyGTK. I could be wrong there though. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] If P2 modules are built for PyYaml and Markupsafe, then recommend P2
On 10/29/20 5:22 AM, Pierre Labastie via blfs-dev wrote: As the subject says... But another possibility is to not propose P2 modules at all for those packages. I'm almost sure nothing uses P2 modules for those packages: Markupsafe is here only for Mako and Jinja2, and we build only P3 for those packages. PyYAML is optional for llvm and kf5, and I think those use P3 only now... Let's drop p2 from instructions where it is not needed by something in the book. I do not see a problem with having p2 as an optional dependency though. Looking I now see p2 instructions for D-Bus Python, PyCairo-1.18.2, PyGObject-2.28.7, libxml2-2.9.10, lxml, MarkupSafe, PyYAML, and six. However as best I can tell in the python modules section only PyCairo-1.18.2, PyGObject-2.28.7, and libxml2-2.9.10 need p2. Of course the biggest problem appears to be those packages that need pygtk which uses PyGObject-2.28.7 and PyCairo-1.18.2. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] If P2 modules are built for PyYaml and Markupsafe, then recommend P2
As the subject says... But another possibility is to not propose P2 modules at all for those packages. I'm almost sure nothing uses P2 modules for those packages: Markupsafe is here only for Mako and Jinja2, and we build only P3 for those packages. PyYAML is optional for llvm and kf5, and I think those use P3 only now... Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
