From owner-freebsd-questions@FreeBSD.ORG Mon Nov 26 20:15:41 2012 Return-Path: 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 81C585EB for ; Mon, 26 Nov 2012 20:15:41 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 262BC8FC0C for ; Mon, 26 Nov 2012 20:15:40 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Td55k-0005NM-Sf for freebsd-questions@freebsd.org; Mon, 26 Nov 2012 21:15:47 +0100 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 26 Nov 2012 21:15:44 +0100 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 26 Nov 2012 21:15:44 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Subject: Re: When Is The Ports Tree Going To Be Updated? Date: Mon, 26 Nov 2012 20:15:18 +0000 (UTC) Lines: 30 Message-ID: References: <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com> <50B2BEE1.9030903@tundraware.com> <05eafe033134e0771d54dec2d9388c8f@homey.local> <50B3BA6E.7060303@tundraware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20100101 Firefox/16.0) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 20:15:41 -0000 Tim Daneliuk tundraware.com> writes: > ... > One wonders if using svn to keep the ports tree up-to-date might not be > simpler, and perhaps, more reliable ... As managed by portsnap: $ du -hs /usr/ports/ 850M /usr/ports/ As managed by svn (it took much longer to checkout/download it by comparison): $ du -hs /usr/local/ports/ 1.4G /usr/local/ports/ $ du -hs /usr/local/ports/.svn/ 702M /usr/local/ports/.svn/ One thing about svn is that it is a developer's tool, with its own commands set (that should never be mixed with UNIX commands w/r to dir/file manipulation), and that should not be expected to be learned by non-devs. For that reasons alone the portsnap-managed ports repo is more generic, flexible to be handled by user and add-on apps/utilities, looks like more efficient without that svn overhead resulting from its requirements and characteristics as a source control system. But, svn offers to a user a unique view into ports repo, e.g. history, logs, info, attributes, etc. jb