Date: Tue, 18 Jun 2013 12:54:37 -0400 From: Nikolai Lifanov <lifanov@mail.lifanov.com> To: Andre Oppermann <andre@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Tijl Coosemans <tijl@coosemans.org>, src-committers@freebsd.org, Peter Wemm <peter@FreeBSD.org> Subject: Re: svn commit: r251886 - in head: contrib/apr contrib/apr-util contrib/serf contrib/sqlite3 contrib/subversion share/mk usr.bin usr.bin/svn usr.bin/svn/lib usr.bin/svn/lib/libapr usr.bin/svn/lib/libap... Message-ID: <51C090CD.3040102@mail.lifanov.com> In-Reply-To: <51C08F58.2070308@freebsd.org> References: <201306180253.r5I2rj45053959@svn.freebsd.org> <51C08D7E.2000605@coosemans.org> <51C08F58.2070308@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/18/13 12:48, Andre Oppermann wrote: > On 18.06.2013 18:40, Tijl Coosemans wrote: >> On 2013-06-18 04:53, Peter Wemm wrote: >>> Author: peter >>> Date: Tue Jun 18 02:53:45 2013 >>> New Revision: 251886 >>> URL: http://svnweb.freebsd.org/changeset/base/251886 >>> >>> Log: >>> Introduce svnlite so that we can check out our source code again. >>> >>> This is actually a fully functional build except: >>> * All internal shared libraries are static linked to make sure there >>> is no interference with ports (and to reduce build time). >>> * It does not have the python/perl/etc plugin or API support. >>> * By default, it installs as "svnlite" rather than "svn". >>> * If WITH_SVN added in make.conf, you get "svn". >>> * If WITHOUT_SVNLITE is in make.conf, this is completely disabled. >>> >>> To be absolutely clear, this is not intended for any use other than >>> checking out freebsd source and committing, like we once did with >>> cvs. >>> >>> It should be usable for small scale local repositories that don't >>> need the python/perl plugin architecture. >> >> This ties the repo to the oldest supported release, meaning that years >> from now we won't be able to use some new subversion feature because >> an old FreeBSD release doesn't support it. > > AFAIK there is a checkout-only SVN client available, as in cvsup, but I > don't > remember the name. > >> I don't find it unreasonable to ask developers to install the port. >> And for users it seems all they need is something like portsnap for base. >> Portsnap already distributes ports svn so it shouldn't be too hard to >> adapt it for base. And the extra layer it adds is very convenient. Apart >> from a bigger than usual update maybe, portsnap users never even noticed >> it was switched from cvs to svn at some point. > > Installing SVN from ports is very painful because of the huge dependency > chain it carries, with the largest being Python and Perl IIRC. > It's net/svnup and is a great replacement for cvs, in my opinion. CVS wasn't used for development for a long while anyway, so there is nothing subversion is replacing that net/svnup wouldn't. - Nikolai Lifanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51C090CD.3040102>