From owner-freebsd-ports Wed Dec 20 4:26:15 2000 From owner-freebsd-ports@FreeBSD.ORG Wed Dec 20 04:26:13 2000 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4C77837B400; Wed, 20 Dec 2000 04:26:13 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBKCQAb18928; Wed, 20 Dec 2000 04:26:10 -0800 (PST) Date: Wed, 20 Dec 2000 04:26:10 -0800 From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: asami@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: ports lockfile? Message-ID: <20001220042610.Q19572@fw.wintelcom.net> References: <20001219113535.Q19572@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Wed, Dec 20, 2000 at 01:23:18PM +0100 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Dag-Erling Smorgrav [001220 04:23] wrote: > Alfred Perlstein writes: > > Usually when doing an install I'll start building several ports in > > at the same time The problem is that frequently the ports will > > recurse into the same dependancy, and the two builds will clobber > > each other. > > Use porteasy and specify all the ports you want to build on the > command line, then go have lunch. Sorry... I thought ports by themselves should be easy enough. :) I'll check out porteasy though, thanks. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message