Comment 4 for bug 648246

Is anyone working on this at the moment? If I recall correctly, there was a bit of a push on it a year ago, but I haven't heard anything for a while.

Anyway, I did a quick comparison with the upstream git repo... it looks like we branched immediately after the libcroco-0.6.0 release [1]. If no one is working on this, I propose that we do the same thing as the GDL merge job:

1. Grab the diff from libcroco-0.6.0 to libcroco-0.6.0+inkscape (i.e., our fork).

2. Merge all upstream changes into our fork. [The easiest way is to branch the upstream git repo at version 0.6.0, apply our complete patch, and then do a git merge with master]

3. Pull the merged version back into Inkscape.

4. See which differences remain between libcroco-master and libcroco-master+inkscape.

5. Split the remaining diff into individual patches and submit each of them upstream.

6. After an upstream release is available with all the required changes, update devlibs + encourage linux distros to upgrade their libcroco packages.

7. Update config to build against external libcroco

8. Remove our fork.

Any thoughts?

[1] http://git.gnome.org/browse/libcroco/commit/?id=3e0fb4e6acd9b29303384da9242b08c70e4d9add