Date: Fri, 25 Jan 2013 15:12:03 +0200 From: Daniel Kalchev <daniel@digsys.bg> To: freebsd-stable@freebsd.org Subject: Re: svn - but smaller? Message-ID: <510284A3.8030509@digsys.bg> In-Reply-To: <CAGE5yCpGWiGpeJSJzJGq0SB74nJ-b%2BFEWgAM7b%2BXqK5u8HpEog@mail.gmail.com> References: <20130123144050.GG51786@e-Gitt.NET> <87mww00w89.fsf@Shanna.FStaals.net> <20130123153724.GA79995@e-Gitt.NET> <510007F4.20701@sentex.net> <1358960762-2331017.37282719.fr0NH5PFb026896@rs149.luxsci.com> <CAGE5yCpGWiGpeJSJzJGq0SB74nJ-b%2BFEWgAM7b%2BXqK5u8HpEog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.01.13 21:09, Peter Wemm wrote: > On Wed, Jan 23, 2013 at 9:05 AM, Isaac (.ike) Levy > <ike@blackskyresearch.net> wrote: > >> 1) License. Many of SVN's dependencies will never be available in the FreeBSD source. >> While this is totally OK for development, SVN is 3rd party software, this is unacceptable to force as 'the' respected path for OS source builds. > Don't confuse the excessive ports default settings as dependencies. > You can make a quite mean and lean svn client. I did a 100% > BSD-license-compatible src/contrib/svn style proof-of-concept back > when we were planning what to do. Things like gdbm and bdb are not > required and are license contamination that we don't need. But that's > the fault of the port, not a fundamental property of using svn. > The logical question is then: Why is this slimmed down, fully BSD license compatible svn not in the base system by now? It is absurd to require the installation of any port, if your only intention is to update the base system sources. Portsnap is an entirely different mess. Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?510284A3.8030509>