Ken Moffat wrote:
My first example of breakage from building the libxml2 python module
with python3:
make[1]: Entering directory '/scratch/working/gimp-help-2.8.2/quickreference'
/bin/mkdir -p xml
../tools/xml2po.py -p po/ca.po ./gimp-keys.xml > xml/gimp-keys-ca.xml
Traceback (most recent call last):
File "../tools/xml2po.py", line 190, in <module>
main(sys.argv[1:])
File "../tools/xml2po.py", line 87, in main
from xml2po import Main
File "/scratch/working/gimp-help-2.8.2/tools/xml2po/__init__.py", line 27, in
<module>
import libxml2
ImportError: No module named libxml2
make[1]: *** [Makefile:451: xml/gimp-keys-ca.xml] Error 1
At the moment the Note in libxml2 says:
Some packages which utilize libxml2 (such as GNOME Doc Utils) need
the Python module installed to function properly and some packages
will not build properly if the Python module is not available.
I'm reading that to say that gnome doc utils is OK with using
python3, but I don't build that so I don't know.
Not sure how best to approach this - I suppose we need to optionally
build the module with python2 as well as with python3. And note
that on the package(s) which need the version built with 2.
Will need to look to see if it is easy to build / install only the
v2 module.
But as soon as I've installed the v2 module I'll not notice what
needs it. Tricky.
Sometimes we just need to wait for reports from users to identify
infrequent problems like this.
It might help to send support requests to fix this to upstream packages
like gimp.
This is what arc does for libxml2:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/libxml2
but theirs is a bit more complicated because they have python==python3 and
have to work around those packages that assume otherwise.
Personally, I'd like upstream to convert everything to py3 and let py2 go
away,
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
