From owner-freebsd-current@FreeBSD.ORG Tue Aug 9 18:04:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 700AA16A41F; Tue, 9 Aug 2005 18:04:41 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 083B043D5C; Tue, 9 Aug 2005 18:04:40 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by postfix3-1.free.fr (Postfix) with ESMTP id CD37817349B; Tue, 9 Aug 2005 20:04:38 +0200 (CEST) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id j79I4Vrk014320; Tue, 9 Aug 2005 20:04:36 +0200 (CEST) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Tue, 9 Aug 2005 20:03:59 +0200 User-Agent: KMail/1.8.2 References: <42F871B4.6000703@freebsd.org> <200508091902.57044.thierry@herbelot.com> <42F8E5B0.9000709@freebsd.org> In-Reply-To: <42F8E5B0.9000709@freebsd.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200508092004.09405.thierry@herbelot.com> Cc: freebsd-ports@freebsd.org, Colin Percival Subject: Re: Portsnap is now in the base system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2005 18:04:41 -0000 Le Tuesday 9 August 2005 19:19, Colin Percival a écrit : > > > > I've had a look at the man page(s), and at the web page on > > http://www.daemonology.net/portsnap/ I'm still missing one piece of > > information : how are the ports snapshots initially built ? > > Magic. :-) I *knew* it. > > Seriously, I checkout a copy of the ports tree, run `make describes` three > times (for 4.x, 5.x, and 6.x), package up the resulting files, build some > patches, and then throw everything onto my web server. From there it gets > mirrored by another server (and more mirrors will follow). > > Once I've ironed out all the bugs in the building and mirroring, I'll make > that code available via the projects repository. fine > > > One misfeature of cvs is the possibility to fetch incomplete updates to > > the repository (no atomic commits in cvs, and this must be carried over > > to cvsup). Do "your" snapshots behave better in this domain ? > > No. I take a snapshot of the files on cvsup-master (via cvsup over an ssh > tunnel -- being a committer hath its privileges :-) ), and that's what I > package up, with the one exception that if the INDEX build is broken then > users will get the most recent unbroken INDEX instead. > > > As one last question : I assume the same process of building "coherent" > > snapshots could be also applied to the core cvs repository of the full > > FreeBSD project, and a cvs-snap utility could be imagined ? > > This process doesn't build coherent snapshots; and the same process > wouldn't work very well for anything other than ports due to a number of > reasons concerning the structure of the ports tree and the lack of > structure of the non-ports trees. too bad : as you demonstrated, the project makes good use of "assured" methods of disseminating new software - these are two very important stepping stones and it's just a pity not to have the same kind of tool for the core of the OS = the source (and it's too late for a SoC project ...) > > Colin Percival TfH