On Thu, Jul 26, 2007 at 04:02:48PM +0200, Marco Spinetti wrote: > I don't know if this versioning problem is a good news or not. > For example RHEL 3 has python 2.2.3: so I suppose that it's no possibile > to use tha last versions of libxslt. > It's a bad news.
The *only* solution to avoid this kind of problem is to not code anymore on libxml2 or libxslt. If you really want to backport, then do it, but as I said it does take time and expertise, running old systems is NOT CHEAP. The way you can do this is the following, go back to the diffs between 2.6.16 and 2.6.17, find the enhancement of libxml2 and libxslt which added support for booleans in XPath from python. Get a revert patch, use that patch on recent release, do the QA to make sure this doesn't break other libxml2 python apps (like for example RHEL installer) and then keep your forked version. Other way try to find how to still prvide that capability an compile on version of python who don't export boolean type info at their C interface. You cannot have the old system and the new piece without also the cost of doing the exercise. I'm already extremely careful and cautious to not break old platforms but sometimes you have to make progress, the only solution otherwise is no progress and then people will complain it doesn't work on the *newer platform*. What you are asking for is a very costly operation. The open source project can't really do that for you, I guess you must assume the cost (in time at least) needed by your own constraints. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xml mailing list, project page http://xmlsoft.org/ [email protected] http://mail.gnome.org/mailman/listinfo/xml
