The Mobile Robot Programming Toolkit

Up to now, the Subversion repository used to develop MRPT was sited and maintained at the Málaga University, but to assure a greater reliability in the future, we just finished moving it to the servers of Google Code.

Q: I downloaded MRPT as zip or tar.gz files, I try to be away of weird stuff such as that SVN thing...

A: That's your case, then can stop reading this! You're not affected at all.

Q: I have a local checkout of MRPT from the previous server. Will it continue working?

A: Nope. That local copy won't be able to do any further update. The recommendation is to delete it, then do a new fresh checkout from the new Google code server.

Q: But I have local (non committed) modifications! Will I lose my changes?

A: Nothing will be lost... if the transition is done carefully following these steps:

1. Create a diff of your changes. From a console, go to your current MRPT root directory and do a svn diff > MY_CHANGES.diff and save that file at some safe place. Alternative for Windows users: With TortoiseSVN, right-click on the MRPT root directory -> "Create patch..." and save your .diff file.
2. Checkout from new repository. Do an authenticated checkout in a new directory, as explained in http://code.google.com/p/mrpt/
3. Apply saved changes. From a console, go to the new MRPT directory and do patch -p0 < MY_CHANGES.diff . Alternative for Windows users: With TortoiseSVN, right-click on the ROOT directory of the new MRPT local copy -> "Apply patch..." -> Select your MY_CHANGES.diff file -> Select "Apply all".
4. Review, and optionally, commit. You can now move or delete the old local copy of MRPT, and try to build the new one with your changes applied. If everything goes OK (and want to do so), you can now commit the changes to the new SVN server.

Q: What happened to my USVN account?

A: It's now not needed at all. See the next point below.

Q: How to gain write access to the repository?

A: Authentication is now done via Google accounts (GMail accounts are OK). If you're not listed as "committer" at the Google code web, email one of the project owners listed in that same page asking for write access.