From owner-freebsd-questions@FreeBSD.ORG Tue Nov 27 16:02:37 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 C73DCBF7 for ; Tue, 27 Nov 2012 16:02:37 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id 8BDD28FC08 for ; Tue, 27 Nov 2012 16:02:37 +0000 (UTC) Received: from 24-181-237-39.dhcp.oxfr.ma.charter.com ([24.181.237.39] helo=Gregory-Larkins-iMac.local) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1TdN49-000GCE-5V; Tue, 27 Nov 2012 10:27:24 -0500 Received: from Gregory-Larkins-iMac.local (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by Gregory-Larkins-iMac.local (Postfix) with ESMTPS id C854017FDEB5; Tue, 27 Nov 2012 10:27:15 -0500 (EST) Message-ID: <50B4DBD3.2050901@FreeBSD.org> Date: Tue, 27 Nov 2012 10:27:15 -0500 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Damien Fleuriot 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> In-Reply-To: X-Enigmail-Version: 1.4.6 X-SA-Exim-Connect-IP: 24.181.237.39 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.1 Subject: Re: When Is The Ports Tree Going To Be Updated? Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: jb , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2012 16:02:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/27/12 4:36 AM, Damien Fleuriot wrote: > On 26 November 2012 21:15, jb wrote: >> 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 >> > > While we're on the binary vs SVN topic, I'd like to point out I'm > *actually running out of inodes* on a virtualized machine (we use > these a lot for our dev and preproduction environments) with 5gb > of space, when checking out the ports tree. > > Of course 5gb is quite small but then, this was installed a while > back. > > The transition to SVN means I'm going to have to reinstall these > firewalls. There are a lot of them it's going to be a major pain. > > > idk, I'm loathe to use portsnap, I liked CSup just fine. 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. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC029MACgkQ0sRouByUApBC5QCfZeDivNGRMWB4DV4usXGLojrv lBsAoIWG4O/ekYRiGJI0M238v+J1y/Lx =wHdv -----END PGP SIGNATURE-----