From owner-freebsd-stable@FreeBSD.ORG Thu Jan 24 11:30:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3735A172 for ; Thu, 24 Jan 2013 11:30:35 +0000 (UTC) (envelope-from jcm@visi.com) Received: from g2host.com (mailback4.g2host.com [208.42.184.244]) by mx1.freebsd.org (Postfix) with ESMTP id EC30969 for ; Thu, 24 Jan 2013 11:30:34 +0000 (UTC) Received: from [208.42.90.57] (account jcm@visi.com) by mailback4.g2host.com (CommuniGate Pro WEBUSER 5.3.11) with HTTP id 11496645 for freebsd-stable@freebsd.org; Thu, 24 Jan 2013 05:30:33 -0600 From: "John Mehr" Subject: Re: svn - but smaller? To: X-Mailer: CommuniGate Pro WebUser v5.3.11 Date: Thu, 24 Jan 2013 05:30:33 -0600 Message-ID: In-Reply-To: References: <20130123144050.GG51786@e-Gitt.NET> <20130124093846.5e683474@laptop> MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1; format="flowed" Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 11:30:35 -0000 On Thu, 24 Jan 2013 18:34:33 +1100  "Dewayne" wrote: > 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. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to >"freebsd-stable-unsubscribe@freebsd.org" > Hello all, I'm working on writing a lightweight, dependency-free, BSD licensed program to pull source using the svn protocol (not using the aforementioned svnsup code).  I've only got a few more pieces of the puzzle to sort out and some code cleanup and it should be ready for testing. As someone who has never contributed code, what's the best way to submit this code for consideration?  Do I just slap a BSD license on it and post it to the list?  Do I first create a port for it?  Also, does anyone know who I should contact regarding permission to test my code against the repository at svn.freebsd.org?  Thanks.