Re: Managing package sources with subversion?
Joey Hess wrote:
- cvs2svn works ok, but can be _very_ slow. Be prepared for significant
archive bloat too. I also had to run it three times due to some
subversion bug that I have supressed memory of.
I didn't bother importing all the history of tn5250 from CVS into
Subversion. The old changes are still in CVS if I need them.
[snip]
- After I imported mooix into subversion, I went back and de-munged all
the tags generated by cvs-buildpackage. cvs has limits on tag names
(no periods allowed) so you probably have ugly tags like
debian_version_1_01 and so on. You can use svn mv, pointed directly at
the repo, to rename these tags to debian_version_1.01 or whatever you
feel is appropriate.
I eventually decided that there was no particular reason to use the tags
directory for Debian versions, and created a new "debian" directory:
% svn ls file:///home/repos/debian/tn5250
branches/
debian/
tags/
trunk/
vendor/
% svn ls file:///home/repos/debian/tn5250/debian
0.16.5-1/
0.16.5-2/
0.16.5-3/
0.16.5-4/
0.16.5-5/
% svn ls file:///home/repos/debian/tn5250/vendor
0.16.5/
current/
The branches and tags directories are both empty.
[snip]
Or you can use subversion's nice fast export command to get a clean
export without the .svn directories and build in there. Note that svn
export copies the tree, including any uncommitted changes, which is
both good and bad. You can use it while offline. I'm probably going to
switch to using this technique.
Ooh, I missed this option for svn export. Thanks.
--
"Hanging is too good for a man who makes puns; he should be drawn and
quoted."
-- Fred Allen
Reply to: