From owner-freebsd-ports@FreeBSD.ORG Thu Jul 3 15:33:54 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 6D33C1065675 for ; Thu, 3 Jul 2008 15:33:54 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.freebsd.org (Postfix) with ESMTP id 24D6C8FC18 for ; Thu, 3 Jul 2008 15:33:54 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from dhcp250-210.yandex.ru ([87.250.250.210]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1KEQoh-0007DY-PQ; Thu, 03 Jul 2008 19:33:51 +0400 Message-ID: <486CF15B.50309@FreeBSD.org> Date: Thu, 03 Jul 2008 19:33:47 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Robert Huff References: <20080702232551.GA3204@pcjas.obspm.fr> <486CD2E8.50505@FreeBSD.org> <18540.55980.938489.721330@jerusalem.litteratus.org> In-Reply-To: <18540.55980.938489.721330@jerusalem.litteratus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Albert.Shih@obspm.fr, FreeBSD-Ports@FreeBSD.org 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 15:33:54 -0000 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. It's not a ruby issue. Now you can run a few portupgrade processes if sets of updating ports is not intercepted. Otherwise one portupgrade process can clear a port directory when another process build the port. -- Dixi. Sem.