From owner-freebsd-ports@FreeBSD.ORG Thu Jul 3 21:15:34 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E96BA1065685 for ; Thu, 3 Jul 2008 21:15:34 +0000 (UTC) (envelope-from fbsd06+XP=609639b6@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id C89BD8FC15 for ; Thu, 3 Jul 2008 21:15:34 +0000 (UTC) (envelope-from fbsd06+XP=609639b6@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by fallback-in1.mxes.net (Postfix) with ESMTP id 900151646ED for ; Thu, 3 Jul 2008 17:00:16 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id B4E1A23E4AF for ; Thu, 3 Jul 2008 17:00:14 -0400 (EDT) Date: Thu, 3 Jul 2008 22:00:09 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20080703220009.4da5ff08@gumby.homeunix.com.> In-Reply-To: <18540.55980.938489.721330@jerusalem.litteratus.org> References: <20080702232551.GA3204@pcjas.obspm.fr> <486CD2E8.50505@FreeBSD.org> <18540.55980.938489.721330@jerusalem.litteratus.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Idea for next portupgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2008 21:15:35 -0000 On Thu, 3 Jul 2008 09:57:00 -0400 Robert Huff wrote: > > Sergey Matveychuk writes: > > > > If portupgrade can calculate the depency and launch many ports > > > build in same time for non-depending ports it's can be > > > wonderful. > > > > I'm sure it's a good idea. I'd use it too. But I have a very > > little free time with my current employment. So I can't implement > > it. Sorry. > > It is also my understanding that ruby (used to manage the > ports database) a) is not re-entrant and/or b) does not lock the > files it is using/changing. Having two instances running at once > causes Bad Things(tm) to happen. Presumably most of the work can be done in parallel with the critical stages serialised. There's already a build tool that builds several ports in parallel, I presume that's how it works. I can't remember what it's called offhand.