Date: Tue, 18 Jun 2013 18:40:30 +0200 From: Tijl Coosemans <tijl@coosemans.org> To: Peter Wemm <peter@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@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: <51C08D7E.2000605@coosemans.org> In-Reply-To: <201306180253.r5I2rj45053959@svn.freebsd.org> References: <201306180253.r5I2rj45053959@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2KGPOJVHLDIHBNGLULNII Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 >=20 > Log: > Introduce svnlite so that we can check out our source code again. > =20 > 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. > =20 > 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= =2E > =20 > 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. 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. ------enig2KGPOJVHLDIHBNGLULNII Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iF4EAREIAAYFAlHAjYMACgkQfoCS2CCgtit+0wD/abEktKdy/kKyCUC/QXdvfoEZ 9HMV/efB4kxfgK7QFtEA/3vhaXNDBHTfcmpI/+vsCEGpUHEvOjM4qsNcV6ae+dsl =NNrN -----END PGP SIGNATURE----- ------enig2KGPOJVHLDIHBNGLULNII--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51C08D7E.2000605>