cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)

[Paweł Sakowski]

On Fri, 2005-09-09 at 22:48 +0200, Tomasz Pala wrote:
> 1. building a package from given branch:
> cvs:	./builder -bb -R foo bar or ./builder -g and rpmbuild -bb
> svn:	!? rpm uses SPECS/SOURCES subdirs,[...]

Untrue. rpm uses macros. The way the macros are currently defined uses
SPECS/SOURCES subdirs. A quick-and-unperfect %(pwd) in the appropriate
place would make it:

svn co .../foo;cd foo;rpmbuild foo.spec

> 2. updating all resources I've checked out (having CVS/Entries.Static):
> cvs:	cd SPECS, cvs up; cd ../SOURCES; cvs up
> svn:	!?

svn up */*

> 5. reverting a commit:
> cvs:	cvs up -r X foo; mv foo{,.tmp}; cvs up -A foo; mv -f foo{.tmp,}; cvs ci foo

Easier:
cvs up -j X -j HEAD foo;cvs ci foo
(maybe the other way round... I don't remember the exact -j syntax)

> svn:	svn revert foo

You mean `svn merge -r...:... foo;svn ci foo`. `svn revert foo` is
actually an equivalent of:

rm foo;cvs up -A foo

or equivalently (a fun hack for non-binary files)

cvs diff foo|patch -R

> no difference for me. Not an argument.

The difference is that with CVS you're playing file-by-file, with svn
you can revert a whole commit{, series}, just by knowing {its,their}
revision number{,s}.

-- 
Paweł Sakowski <saq at pld-linux.org>
PLD Linux Distribution