migrating to pyshapelib repository

[Bram de Greve]

Hi Bernard,

As the new pyshapelib has been merged into the trunk of thuban, it
perhaps is time to separate pyshapelib into its own project, as you
suggested before?

If you're ready to create a new project and repository, this is how you
can copy the history of pyshapelib to the new repository.  Bear with me,
although it's only three simple steps, it's quite a bit of typing
because of the many branch names.

DISCLAIMER: obviously, I wasn't able to test them.  But I _think_
they're (about) right.


1. we need to get a dump of the thuban repository. This dump might
become quite large. Possibly, you can directly pipe it into step 2.

svnadmin dump /path/to/svn/thuban > thuban.dump


2. we need to filter the pyshapelib stuff (I propose we keep a mirror of
the necessary shapelib sources for easy access).  We need to retain a
few branches here.  So quite a few arguments =)  thuban.dump goes in,
pyshapelib.dump comes out.

svndumpfilter --drop-empty-revs include \
  trunk/thuban/libraries/pyshapelib \
  trunk/thuban/libraries/shapelib \
  branches/WIP-pyshapelib-bramz/thuban/libraries/pyshapelib \
  branches/WIP-pyshapelib-bramz/thuban/libraries/shapelib \
  branches/WIP-pyshapelib-Unicode/thuban/libraries/pyshapelib \
  branches/WIP-pyshapelib-Unicode/thuban/libraries/shapelib <
thuban.dump > pyshapelib.dump
 
 
2 + 1/2. Now in theory, it's possible to tweak this cute dump file to
surgically remove the 'thuban/libraries' part from the path names.  But
I suggest we don't that, and do an 'svn move' from
trunk/thuban/libraries to trunk afterwards.

 
3. Finally, you should be able to load the filtered dump in the fresh
repository

svnadmin load /home/svn/pyshapelib < pyshapelib.dump


Hopefully this will actually work =)

Cheers,
Bram