From owner-freebsd-questions@FreeBSD.ORG Tue Nov 27 09:36:35 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 CB691B53 for ; Tue, 27 Nov 2012 09:36:35 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8615C8FC13 for ; Tue, 27 Nov 2012 09:36:34 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so14407295iec.13 for ; Tue, 27 Nov 2012 01:36:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=QQ7RpAJJphI2Q8Tok3bnmRcce3HIF+ljVZfxcNkJreo=; b=kWYn8VVpzUX5wzm9VNo+9P7mG0jLqimvDDQYx9l5Vyao/yEC2Wmb/+toWgckoL9WV2 e51KqNbjT0IT7wBBGQ3+fr45wCUHUnpzr3EZTarnvcxFLSifS+8+OaA5Y6eua6zMAuH8 LtGprqWW0GpBaYHQ5QYbugfuMKOyaRFofzb9mN4qVJ06DsZclPQbewEkViFn1y+G9Noj MvrQjXjj1EEQFku79KJt0y5x14+sYSWbZjMJaJrB7H0SrSG4uZuzkDWAv2D5uMfOaWk2 emb+39DCVUwxu1aKmkStP/uP3a0L4oTnrYEfEOfU/FySnGcuteGvdzSfBrdZy6151cK4 wJPQ== MIME-Version: 1.0 Received: by 10.50.178.106 with SMTP id cx10mr17745348igc.24.1354008994189; Tue, 27 Nov 2012 01:36:34 -0800 (PST) Received: by 10.64.147.34 with HTTP; Tue, 27 Nov 2012 01:36:33 -0800 (PST) In-Reply-To: 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> Date: Tue, 27 Nov 2012 10:36:33 +0100 Message-ID: Subject: Re: When Is The Ports Tree Going To Be Updated? From: Damien Fleuriot To: jb Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnVtIWTAB4TeqSw+sfG/yhnwoOOyQaM97U9vqRWt5oC7CJGTRxOaEtxyW3MiKg1UL/KPFHt 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 09:36:35 -0000 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.