On Fri, 5 Nov 2004, Gaetano Mendola wrote:
Peter Eisentraut wrote:
I'm certainly open to considering subversion, although I have a certain traumatic experience with it that may or may not be related to the BDB backend that it uses.
I think for a start it would be nice if pgfoundry could optionally offer subversion (and/or arch) for source control, so that some developer groups and also our system administrators could get some experience with it.
I good very start point is see if cvs2svn can handle the postgresql CVS without
errors.
I tried that yesterday out of curiosity. It had problems with 3 files which I removed manually:
/pgsql/src/interfaces/perl5/Attic/ApachePg.pl,v /pgsql/src/interfaces/perl5/Attic/test.pl.newstyle,v /pgsql/src/interfaces/perl5/Attic/test.pl.oldstyle.pl,v
Otherwise, no problems.
Interestingly, the subversion repository is 585MB, and the CVS repository is only 260MB, so apparently Subversion is not very good at compressing the repository. Not that it matters, though.
FWIW, I think Peter's idea of offering Subversion as an alternative in pgfoundry is very good.
I also agree with Andrew's observation that it's really up to the committers since they are the ones that have to work with whatever system we have.
I like subversion very much, but one thing that troubles me a bit is the number of extra libraries required to compile and run it. Also, is there pre-compiled binaries for all the platforms that PostgreSQL supports?
- Heikki
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
