[osgeo4w-dev] [osgeo4w] #331: update libxml2 to 2.9.0
OSGeo4W
trac_osgeo4w at osgeo.org
Mon Dec 31 11:51:29 PST 2012
#331: update libxml2 to 2.9.0
------------------------+---------------------------------------------------
Reporter: aperi2007 | Owner: osgeo4w-dev@…
Type: enhancement | Status: new
Priority: major | Component: Package
Version: | Keywords:
------------------------+---------------------------------------------------
Comment(by aperi2007):
mmh....
I guess probably no, but I'm not sure of this.
I see these reports that say all the changes between libxml2 versions.
[http://upstream-tracker.org/versions/libxml2.html]
As it say the only two suspectable release that could break compatibility
are
2.6.22 to 2.6.23
and
2.8.0 to 2.9.0
The total incompatibility are about 6.58&%
as reported from here.
[http://upstream-
tracker.org/compat_reports/libxml2/2.6.22_to_2.6.23/abi_compat_report.html#Medium_Risk_Problems]
[http://upstream-
tracker.org/compat_reports/libxml2/2.8.0_to_2.9.0/abi_compat_report.html#Medium_Risk_Problems]
So I guess it is pretty incompatibility.
So perhaps libxml 2.9.0 is not a good update as is.
But tinyows 1.0.0 rc4 is really used as is now on ogeo4w ?
The previsous version of libxml2 has a knowed GML bug that need to do some
manual changes on libxml2 himself to use with tinyows (rc4 also).
[http://mapserver.org/trunk/tinyows/libxmlschemagmlbug.html]
So perhaps just now is the tinyows 1.0.0 rc4 that don't work very well
with a libxml2 2.6 is that library was not manual patched ?
--
Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/331#comment:2>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.
More information about the osgeo4w-dev
mailing list