Erik Trulsson wrote: > > > > > > I would be happy to use svn as I do for my own projects. > > > > > > To run a cvs repository, you just need /usr/bin/cvs started from > > > inetd. It is even in the base system. > > > > > > To run a subversion repository, you need much more infrastructure and > > > more overhead (lots of dependencies from ports, probably a Web server, > > > a database backend etc). Besides, cvs is conveniently integrated with > > > Kerberos (we use :gserver: all the time) which I am not sure is > > > possible with subversion. > > > > I have just built and installed ports/devel/subversion on a fresh box. > > The port installed 17 dependent ports: > > Several of which are only build-dependencies. If you were to install > subversion as a package far fewer dependencies would be installed.
I agree, but then it would be compiled with BDB support which I loathe. (I have a reason to loathe BDB after using spamprobe with BDB backend for some time). (Of course, I always have the option to make my own package, I know that). BTW, does svn allow mirroring the whole FreeBSD repository (like cvsup in CVS mode), so that I can later checkout any branch from the local repository? > > Of the ports you list autoconf/automake, libtool, help2man, perl, python, and > tcl (and possibly some more) are only needed when building the port. Sure, but even as a package it would depend on expat-2.0.1 neon28-0.28.6 sqlite3-3.6.19 gdbm-1.8.3_3 libiconv-1.13.1 apr-ipv6-gdbm-1.3.8.1.3.9 -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:[email protected] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
