From owner-svn-src-head@FreeBSD.ORG Wed Jun 19 22:50:07 2013 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2D7334C2; Wed, 19 Jun 2013 22:50:07 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id F196E13BC; Wed, 19 Jun 2013 22:50:06 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r5JMnuAl085884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Jun 2013 22:49:58 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) 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... From: David Chisnall In-Reply-To: <201306191113.29703.jhb@freebsd.org> Date: Wed, 19 Jun 2013 23:49:51 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201306180253.r5I2rj45053959@svn.freebsd.org> <11DA3D8A-AD20-4DE1-B807-D09814F61947@bsdimp.com> <51C1C7BD.9060201@FreeBSD.org> <201306191113.29703.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1503) Cc: src-committers@FreeBSD.org, Andre Oppermann , Peter Wemm , svn-src-all@FreeBSD.org, svn-src-head@FreeBSD.org, Tijl Coosemans , Warner Losh X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 22:50:07 -0000 On 19 Jun 2013, at 16:13, John Baldwin wrote: > portsnap does not work for src. (I thought we had already covered = that > in earlier threads?) portsnap only moves forward. It is a very = important > feature for our users that whatever tool they use for source updating = be > bidirectional. In particular it is very common practice to use a = bisect > operation to isolate changes responsible for regressions. Freebsd-update can manage the src tree. I'm not entirely clear on what = use-case we are addressing here. Is it: - FreeBSD developers, who are probably okay with installing a port, but = would prefer a version that didn't depend on kitchen/sink? - Users, who wish to be able to update the source tree and then either = build world, or build some optional parts that are not part of the = default install? - Some other category of svn consumer? I think having a definitive statement as to the intention of svnlite = would help frame the discussion in a more productive format. David