Re: Bug#819562: RFP: libxml++ series: C++ wrappers for the libxml2 XML parser library
Control: reassign -1 wnpp
Control: clone -1 -2
Control: retitle -1 RFP: libxml++-4.0 -- C++/glibmm-2.68 wrapper for the libxml2 XML parser library
Control: retitle -2 RFP: libxml++-5.0 -- C++ wrapper for the libxml2 XML parser library
On Wed, 30 Mar 2016 at 16:42:05 +0200, Gert Wollny wrote:
the new version 3.0 of libxml++ is out. It can be installed in parallel with
libxml++2.6.
Since then, libxml++-3.0 has itself been superseded by libxml++-4.0 and
libxml++-5.0.
The difference between 3.0 and 4.0 is that 3.0 uses the outdated
glibmm2.4 API/ABI (libglibmm-2.4-dev in Debian), but 4.0 uses the
replacement glibmm2.68 API/ABI (libglibmm-2.68-dev in Debian).
The difference between 4.0 and 5.0 is that 4.0 uses glibmm, but 5.0
removed the glibmm dependency. The price it pays for this is that it "is
not as good at handling UTF-8 strings" (upstream's words). So I think
either 4.0 and/or 5.0 could make sense to package, depending on what
functionality dependent packages want.
Upstream says:
In a new application, choose between libxml++-4.0 with UTF-8 support
and libxml++-5.0 with fewer dependencies.
The GNOME team is the maintainer of record for libxml++2.6, but we're
unlikely to package the replacement libraries, because nothing in GNOME
needs them any more (as far as I can see) and we already have quite a
lot of packages.
Packages in testing/unstable that currently depend on libxml++2.6, and
should ideally be converted to one of the newer libraries, are:
- cherrytree (GTK 3, glibmm 2.4)
- galois (GTK 3, glibmm 2.4)
- gimagereader (GTK 3, glibmm 2.4)
- gobby (GTK 3, glibmm 2.4)
- libcifti0t64 (non-GUI)
- libffado2 (non-GUI)
- libmirwayland-bin (non-GUI)
- libsubtitleeditor0 (GTK 3, glibmm 2.4)
- libsynfig0t64, synfigstudio (removed from testing already) (GTK 3, glibmm 2.4)
- lordsawar (GTK 3, glibmm 2.4)
- ofx (non-GUI)
- performous (SDL 2, glibmm 2.4)
- pinot (GTK 3, glibmm 2.4)
Perhaps maintainers of one of those packages, or someone in the XML/SGML
team, could pick up the libxml++ family?
smcv
Reply to: