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

[wrobell]

On Wed, 2005-09-07 at 11:03 +0200, Jan Rekorajski wrote:
> On Wed, 07 Sep 2005, wrobell wrote:
> 
> > On Tue, 2005-09-06 at 19:27 +0200, Jan Rekorajski wrote:
> > > On Tue, 06 Sep 2005, wrobell wrote:
> > > 
> > > > On Tue, 2005-09-06 at 18:46 +0200, Michal Kochanowicz wrote:
> > > > > On Tue, Sep 06, 2005 at 05:32:50PM +0100, wrobell wrote:
> > > > > > let's start new war...
> > > > > > 
> > > > > > what about moving repo to svn?
> > > > > 
> > > > > Any reasons? SVN sucks a big one.
> > > > 
> > > > svn diff without performing connection to remote server.
> > > 
> > > At the cost of keeping ALL tags/branches locally. You're joking.
> > > 
> > > [baggins at sith rpm]$ du -hs SOURCES SPECS 
> > > 959M    SOURCES
> > > 63M     SPECS
> > 
> > you do _not_ have to keep _all_ tags/branches locally.
> 
> Really? How?
> Example: http://svn.pld-linux.org/svn/rc-scripts
> I want to keep only trunk, branches and _some_ tags, tell me how to do
> it, and how to prevent svn up from getting all tags.

svn up trunk?
svn up tags/tagireallywant?

come on...

> > > > i think that cvs really sucks. so... any alternatives?
> > > 
> > > There is nothing better :/
> > 
> > with cvs we are loosing some information (i.e. deleted branches
> > and tags). svn allows us to track it _easily_.

> And the royal PITA, which svn is, is not worth it.

... it is really hard to discuss with such arguments, which seem
to be matter of taste.

i think (let's skip svn for now), we need:
- to keep history of tags and branches
- atomic commit (so we can commit patches and specs with one move
  and revert it easily later if there is a need)
- ability to rename specs and patches without pain and loosing
  information and _without_administrator_ help
- check changes without making connection to remote server

these are my problems with cvs. svn solves them. 

svn gives us some advantages. disadvantages? any real, which makes life
really painful? let's talk but without "royal PITA", "i do not care
for lost information", "i do not care for renaming", etc. please.

then, if svn is not solution for us, then what other alternatives
we can use? let's think about it, because cvs is not solution
for us.

  wrobell <wrobell at pld-linux.org>