From owner-freebsd-questions@FreeBSD.ORG Tue Nov 27 16:07:27 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 41A1CFE4 for ; Tue, 27 Nov 2012 16:07:27 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id B91CB8FC12 for ; Tue, 27 Nov 2012 16:07:26 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so5365223wey.13 for ; Tue, 27 Nov 2012 08:07:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=XUpLDuRxMlb9bcwqfG7JwgoCvwd8ZP0xaSVNyplCQAY=; b=aWK/9gztmN3VeRhOq2PJNXdJewnw/dtAGCxfAjtsiiyNwK3Hy5RvI9Rtu9ciMfC5ma 7T6V0YMPIuQpyxItw2maO083JwTy750NLZ0FbTKT7EEezoAzgIPQCJct+Ewjc2rPckOY slUMMFlgYxVIh7obT8pjrROpYUTGSoKYv06JjQVZFJFBFs5MJUqKdoELmBIyhgEHKBnl uVWoikjVTad0HmxQ9mHRNMOFMwM3uMo/3GgnSXnBL1p9kDzhN+UrXEDz3sDzAQTZ4Fv2 UuIYewMnonIRL8+G4pGe0BlE4pKpuDranPNYulc3x57qzphy45kyITiIopA0dMnJaces x3/g== Received: by 10.216.227.132 with SMTP id d4mr6188584weq.33.1354032438712; Tue, 27 Nov 2012 08:07:18 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id e6sm3096224wiy.4.2012.11.27.08.07.17 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 27 Nov 2012 08:07:17 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: When Is The Ports Tree Going To Be Updated? From: Fleuriot Damien In-Reply-To: <50B4DBD3.2050901@FreeBSD.org> Date: Tue, 27 Nov 2012 17:07:15 +0100 Content-Transfer-Encoding: quoted-printable 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> <50B4DBD3.2050901@FreeBSD.org> To: glarkin@FreeBSD.org X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQlA5ZUadA5+aAj6BAD8P1ISndAIkmd0oNLd+sjhMV8Fn/KcXhA7CvqpNF7ry3gZYjmRN4l6 Cc: freebsd-questions@freebsd.org 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: Tue, 27 Nov 2012 16:07:27 -0000 On Nov 27, 2012, at 4:27 PM, Greg Larkin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 11/27/12 4:36 AM, Damien Fleuriot wrote: >> On 26 November 2012 21:15, jb wrote: >>> Tim Daneliuk tundraware.com> writes: >>>=20 >>>> ... One wonders if using svn to keep the ports tree up-to-date >>>> might not be simpler, and perhaps, more reliable ... >>>=20 >>> As managed by portsnap: $ du -hs /usr/ports/ 850M /usr/ports/ >>>=20 >>> 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/ >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> But, svn offers to a user a unique view into ports repo, e.g. >>> history, logs, info, attributes, etc. >>>=20 >>> jb >>>=20 >>=20 >> While we're on the binary vs SVN topic, I'd like to point out I'm=20 >> *actually running out of inodes* on a virtualized machine (we use=20 >> these a lot for our dev and preproduction environments) with 5gb >> of space, when checking out the ports tree. >>=20 >> Of course 5gb is quite small but then, this was installed a while >> back. >>=20 >> 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. >>=20 >>=20 >> idk, I'm loathe to use portsnap, I liked CSup just fine. >=20 > 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. >=20 > 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. >=20 > Hope that helps, > Greg >=20 > - --=20 > Greg Larkin Well I definitely don't plan on making changes to local files or = committing stuff, I'd just like to keep an updated ports tree and switch = from CVS to SVN. I guess I'll have a look at svn export, thanks for the tip Greg.