Inkscape conversion update
Ian Clatworthy
ian.clatworthy at canonical.com
Wed Oct 28 09:09:26 GMT 2009
Ted,
As discussed on IRC, I rsync'ed the latest Inkscape repository today
from sourceforge.net and did a conversion of trunk. As requested, here
are the memory requirements (VmPeak value when the -Dmemory option is
used) of the various stages:
1. svn-import: 4.29G (32m22s)
2. fast-export of inkscape/trunk: 609M (4m12s)
3. fast-import of dump file: 865M (8m43s)
For the record, I used bzr 2.0.0 and bzr-svn 1.0.0 as included in karmic.
To make it easy for you to repeat the last 2 steps on the various
sub-projects that interest you, I've created an archive of the output
from stage 1 and uploaded it. You can grab it from
http://people.canonical.com/~ianc/inkscape.bzr-svn-import.tar.bz2
All,
In case you're interested in the process we're using, here are some
details. Inkscape changed their branch organisation back in 2006 and its
enough to confuse svn-fast-export (which only exports up to then when
the bit we care about is after then). :-( svn-import is smart enough to
avoid that pitfall. Having converted via svn-import, we're then doing
fast-export/fast-import for two reasons:
1. We want to map committer names from SourceForge user-ids to actual
email addresses. bzr fast-import makes that easy now.
2. The Inkscape repository has lots of subprojects that make it larger
than necessary. Export/import corrects that.
Ian C.
More information about the bazaar
mailing list