Date: Thu, 24 Jan 2013 18:34:33 +1100 From: "Dewayne" <dewayne.geraghty@heuristicsystems.com.au> To: "'Oliver Brandmueller'" <ob@e-Gitt.NET> Cc: 'Jeremy Chadwick' <jdc@koitsu.org>, freebsd-stable@freebsd.org Subject: RE: svn - but smaller? Message-ID: <E10EBB96DCC143BE8F14FD2982AD84B7@white> In-Reply-To: <20130124093846.5e683474@laptop> References: <20130123144050.GG51786@e-Gitt.NET> <20130124093846.5e683474@laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
The objective is to return to a base build of FreeBSD that performs the expected task of being able to pull source, without having to acquire a port. Regardless of our individual solutions/workarounds, the task is to pull and maintain source. Is the discussion going to result in something like svn-lite that enters into the /usr/src/contrib along with the responsibilities associated with maintaining it? And then we need to take into consideration of being overwriting the "base svn" with a full svn package, if required by the user/admin. The issue involves policy decisions along with ongoing support load, rather than just a good technical solution; which as we've seen in earlier discussions, is sorely needed by the folks doing the development/maintenance. In the meantime, ftp isn't really workable for ongoing updates, and rsync is GPL'ed and can't be in the base system. I build svn from ports with all options off except for: ENHANCED_KEYWORD P4_STYLE_MARKERS STATIC which results in a 4.2MB svn program. Suites me but doesn't address the underlying problem - and I don't think that the plan is to make FreeBSD dependent upon the ports system (for subversion) Regards, Dewayne.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E10EBB96DCC143BE8F14FD2982AD84B7>