From owner-freebsd-ports  Tue Dec 19 11:35:42 2000
From owner-freebsd-ports@FreeBSD.ORG  Tue Dec 19 11:35:40 2000
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 C51FD37B400; Tue, 19 Dec 2000 11:35:35 -0800 (PST)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id eBJJZZi19091;
	Tue, 19 Dec 2000 11:35:35 -0800 (PST)
Date: Tue, 19 Dec 2000 11:35:35 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: asami@FreeBSD.org
Cc: ports@FreeBSD.org
Subject: ports lockfile?
Message-ID: <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
Sender: bright@fw.wintelcom.net
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I'm pretty sure I've mentioned this before, I got a lot of approval
for the idea, but I don't have the time and familiarity with the
ports mk files to do what I propose.

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.

I tried to figure out some way for the ports to use the 'lockf'
utility on the port makefile in order to protect it, but I can't
seem to figure out how and where to use lockf.

We'd need some pre-pre-pre make step to do this I imagine, anyone
want to try to do this?  Is it a good idea?

-- 
-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