From owner-freebsd-security@FreeBSD.ORG Wed Oct 27 16:57:58 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A3A16A4D0 for ; Wed, 27 Oct 2004 16:57:58 +0000 (GMT) Received: from tx5.mail.ox.ac.uk (tx5.mail.ox.ac.uk [163.1.2.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id C08C243D54 for ; Wed, 27 Oct 2004 16:57:57 +0000 (GMT) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from scan5.mail.ox.ac.uk ([163.1.2.177] helo=localhost) by tx5.mail.ox.ac.uk with esmtp (Exim 4.42) id 1CMr7U-0002Mz-Hl for freebsd-security@freebsd.org; Wed, 27 Oct 2004 17:57:56 +0100 Received: from rx5.mail.ox.ac.uk ([163.1.2.168]) by localhost (scan5.mail.ox.ac.uk [163.1.2.177]) (amavisd-new, port 25) with ESMTP id 08988-01 for ; Wed, 27 Oct 2004 17:57:56 +0100 (BST) Received: from gateway.wadham.ox.ac.uk ([163.1.161.253]) by rx5.mail.ox.ac.uk with smtp (Exim 4.42) id 1CMr7U-0002Mr-Gj for freebsd-security@freebsd.org; Wed, 27 Oct 2004 17:57:56 +0100 Received: (qmail 393 invoked by uid 1004); 27 Oct 2004 16:57:56 -0000 Received: from colin.percival@wadham.ox.ac.uk by gateway by uid 71 with qmail-scanner-1.20 (clamscan: 0.67. sweep: 2.18/3.79. Clear:RC:1(163.1.161.203):. Processed in 0.015999 secs); 27 Oct 2004 16:57:56 -0000 Received: from dhcp1203.wadham.ox.ac.uk (HELO ?163.1.161.203?) (163.1.161.203) by gateway.wadham.ox.ac.uk with SMTP; 27 Oct 2004 16:57:55 -0000 Message-ID: <417FD393.3070706@wadham.ox.ac.uk> Date: Wed, 27 Oct 2004 17:57:55 +0100 From: Colin Percival User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: drhodus@machdep.com References: <417EAC7E.2040103@wadham.ox.ac.uk> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-security@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: please test: Secure ports tree updating X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 16:57:58 -0000 David Rhodus wrote: > Is this something that can be used to replace cvsup in a general term > like cvsync ? In theory, maybe, but in practice, no. Portsnap distributes snapshots of the ports tree; it isn't designed for distributing the entire CVS repository. If you tried to use the portsnap build code for distributing the ports repository, you'd find it to be impractically slow, since there are some huge files (INDEX,v is 82.5MB) which would take far too long for my binary diff code to handle. When it comes to using portsnap for distributing snapshots of the src/, doc/, or www/ trees, there are other problems. First, these are branched, which means that lots of different snapshots would need to be created; also, while the ports tree is easily split into bite-sized pieces which tend to change independently of each other (ie, individual ports -- usually a single commit will touch several files, but only within a single port directory), the other repositories don't divide so easily into independent parts. I'm glossing over a few details here, but basically: I've given this some thought, and I think that while portsnap is useful for the ports tree, I don't think it will be very useful for anything else. Colin Percival