On Thu, 2009-07-16 at 15:37 -0300, Alain Mouette wrote: [snip] > Could you explain which SVN version is the same as 0.2.0 ???
Is there something wrong with the archives that I posted ??? :) > Reading SVN-history I was thinking that it should be 2519, because 2520 > is 0.2.1 ... SVN is a little strange to the uninitiated. To get the "right" copy of the tagged 0.2.0 release: svn co http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0 If you have a working copy, the following will be _much_ faster: svn sw http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0 That URL should never change, so it will always be the 0.2.0 release. You can switch back to the trunk with a similar command: svn sw http://svn.berlios.de/svnroot/repos/openocd/trunk In this way, you do not need to know the revision numbers when you want to access a tag. Just find the right directory in tags/ and switch to it from your working copy. This is the _only_ way to access the source code that was used to produce the tarballs, though the release process performs additional magic that has been both documented and automated. Building from this location ensures you have the proper output from 'openocd --version'. You can try building from the different working copies to see the difference in the output. In this way, the output produced by the released archives will show the URL above. If you use 'svn sw', you may need to delete and revert the src/openocd.c before rebuild the tree after a switch. That file uses the URL SVN keywords, and that was the only way I could get it to update. Broken. I have patches to fix the release script pending, but the 0.2.0 release archives were produced by hand and I made sure to get this right. As usual, I should suggest running 'make maintainer-clean' _before_ using the 'svn switch' command. It updates the repository in a similar manner as 'svn up'. Even with maintainer mode enabled, the build system may not handle the switch properly. Caveat utilitor. In the end, I recommend using the released archives and avoiding the Subversion repository tags entirely. The release archives have already been bootstrapped and contain a full ChangeLog; the tagged branch has not and does not (though you can use svn2cl to create one). Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
