Re^2: (sort of OT) cvs/vendor supplied modules/our own modifications

Subversion solves the complaints you listed, including keeping the history when deleting/renaming files. I made the switch from CVS to Subversion a little while back with the help of the online version of a great book, and I've really liked it a lot.

There shouldn't be a fee at all; subversion is licensed under the Apache 1.1 license (but with CollabNet as the copyright holder).

Comment on Re^2: (sort of OT) cvs/vendor supplied modules/our own modifications

Replies are listed 'Best First'.

Re^3: (sort of OT) cvs/vendor supplied modules/our own modifications
by dpavlin (Friar) on Jul 25, 2004 at 22:03 UTC

svn2cvs

cvs2svn

Vendor branches in subversion are just directories. Basic principle is following: You have version 1.0 of vendor (upstream) branch. You do copy (which is cheap in subversion) to your trunk (current working tree). When vendor release version 1.1, you do merge. Subversion will diff vendor version 1.0 and 1.1 and apply changes to your working tree. If there are conflicts, you will get original file, left and right merge, just to make it easier. All that is described in much more details in subversion book.

I must also warn you: if you try subversion branches, you won't be able to go back to CVS :-)

2share!2flame...

[reply]


Perl: the Markov chain saw
	PerlMonks