From owner-freebsd-current@FreeBSD.ORG Tue Sep 28 21:21:30 2004 Return-Path: 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 6F95F16A4CE for ; Tue, 28 Sep 2004 21:21:30 +0000 (GMT) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A56043D31 for ; Tue, 28 Sep 2004 21:21:26 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1 [69.55.238.237]) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id i8SLLM7j093178; Tue, 28 Sep 2004 14:21:22 -0700 (PDT) (envelope-from lists@jnielsen.net) Received: (from www@localhost) by ns1.jnielsen.net (8.12.9p2/8.12.9/Submit) id i8SLLMT6093177; Tue, 28 Sep 2004 15:21:22 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: ns1.jnielsen.net: www set sender to lists@jnielsen.net using -f Received: from csrouter.dcs.byu.edu (csrouter.dcs.byu.edu [128.187.0.58]) by webmail.jnielsen.net (IMP) with HTTP for ; Tue, 28 Sep 2004 15:21:22 -0600 Message-ID: <1096406482.4159d5d27c165@webmail.jnielsen.net> Date: Tue, 28 Sep 2004 15:21:22 -0600 From: John Nielsen To: Randy Bush References: <16729.53003.771498.882796@ran.psg.com> In-Reply-To: <16729.53003.771498.882796@ran.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 / FreeBSD-4.9 X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on ns1.jnielsen.net X-Virus-Status: Clean cc: FreeBSD Current Subject: Re: simultaneous portupgrades X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 21:21:30 -0000 Quoting Randy Bush : > am i correct that there is no shared file consistency/integrity > in the portupgrade stuff, so i can not really run two different > portupgrades at the same time? You are correct that it's not a good habit to get into. If you have a fair idea of what depends on what, you can often get away with doing multiple portupgrades at the same time, but don't be surprised when the 'clean' of one build clobbers the working directory of another. On the plus side, it will usually fail loudly if it fails, so all you lose is time (which you may have lost anyway doing things sequentially). If I only have a handful of out-of-date ports, I will generally try to do two batches at once. I'm better at dividing the batches than I used to be... :) JN