From owner-freebsd-questions@FreeBSD.ORG  Tue Nov 27 16:11:07 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 407F21EC;
 Tue, 27 Nov 2012 16:11:07 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 by mx1.freebsd.org (Postfix) with ESMTP id DF8EF8FC08;
 Tue, 27 Nov 2012 16:11:06 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.5/8.14.5) with ESMTP id qARGB6gl056457;
 Tue, 27 Nov 2012 09:11:06 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id qARGB6jg056454;
 Tue, 27 Nov 2012 09:11:06 -0700 (MST)
 (envelope-from wblock@wonkity.com)
Date: Tue, 27 Nov 2012 09:11:06 -0700 (MST)
From: Warren Block <wblock@wonkity.com>
To: Greg Larkin <glarkin@freebsd.org>
Subject: Re: When Is The Ports Tree Going To Be Updated?
In-Reply-To: <50B4DBD3.2050901@FreeBSD.org>
Message-ID: <alpine.BSF.2.00.1211270907010.56247@wonkity.com>
References: <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org>
 <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com>
 <50B2BEE1.9030903@tundraware.com> <loom.20121126T120530-186@post.gmane.org>
 <05eafe033134e0771d54dec2d9388c8f@homey.local>
 <loom.20121126T161423-178@post.gmane.org>
 <C1998C36-57DF-4ACE-8AF2-09E1885E7176@my.gd>
 <loom.20121126T170433-746@post.gmane.org>
 <loom.20121126T182635-720@post.gmane.org> <50B3BA6E.7060303@tundraware.com>
 <loom.20121126T201404-815@post.gmane.org>
 <CAE63ME5YQ-UJ5z9Mu9-PyxgceK4Gd_oBL4_Pm=e+fp_Z=Mf6_A@mail.gmail.com>
 <50B4DBD3.2050901@FreeBSD.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (wonkity.com [127.0.0.1]); Tue, 27 Nov 2012 09:11:06 -0700 (MST)
Cc: Damien Fleuriot <ml@my.gd>, jb <jb.1234abcd@gmail.com>,
 freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 16:11:07 -0000

On Tue, 27 Nov 2012, Greg Larkin wrote:

> Unless you plan to use svn commands other than checkout in your ports
> tree, I would suggest switching to "svn export" or perhaps the
> svn-export script (http://xyne.archlinux.ca/projects/svn-export/) to
> fetch your ports tree.
>
> The export command will not create the .svn metadata directory and
> will save on inode usage.  Of course, you could also create a new
> virtual disk for /usr/ports and tune it with more inodes if you'd
> rather use svn checkout.

It should be added that a stock svn export will download the entire 
ports tree each time rather than just the diffs.

svn-export from above looks interesting, with the ability to get just 
updates.  No port yet, though.