Hi,

while looking at all apps using libwpg[1] (to prepare for filing bugs to
use the normal libwpg from system once uploaded) I also saw that
inkscape uses some other libraries internally, among them libcroco which
is available in Debian already (libcroro3[-dev].

Can inkscape be built with that? Internal libs are bad
bugfix/security-wise...

Regards,

Rene

libcroco-0.6.1 is not suitable for use in inkscape; the src/libcroco
directory has some modifications as explained in src/libcroco/README.

pjrm.

tags + 427946 upstream
thanks

Which actually says:

  This code is derived from libcroco-0.6.  We hope that the changes will
  find their way into libcroco-0.7 (in some form).

  The main changed file is cr-sel-eng.{c,h}.  The cr-sel-eng in
  libcroco-0.6 is somewhat experimental: it has a few bugs, and the
  interface requires that the XML node storage be libxml2.  The version
  in this directory has a modification of allowing passing in a "vtable"
  of operations so that we can use our preferred representation
  Inkscape::XML::Node.

  Once libcroco-0.7 is widely available (with the vtable interface or a
  functional equivalent), this directory should be removed.

So I'll suggest to keep this bug opened until upstream fixes this issue.

Cheers,

Since this report was opened, there has been a new upstream release
(0.6.2) of libcroco and the src/libcroco/README has been removed from
the Inkscape source tree.  I have asked upstream for an update on the
situation with the bundled library at:
https://answers.launchpad.net/inkscape/+question/123799

Thanks,


Alex

2010/9/2 Alex Valavanis <valavanisalex@gmail.com>:
It was derived from some 0.6.x.
Yes, there is a generic selection engine added that allows us to use
libcroco with our custom XML nodes. We cannot migrate to libxml2
because we are making heavy use of XML tree change notifications, a
feature that is not present in libxml2. We could use upstream libcroco
if this bug was fixed:
https://bugzilla.gnome.org/show_bug.cgi?id=572454
No.

Regards, Krzysztof