From owner-freebsd-ports@FreeBSD.ORG Mon Jan 12 18:02:46 2009 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 65F2F10656C8 for ; Mon, 12 Jan 2009 18:02:46 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 495158FC13 for ; Mon, 12 Jan 2009 18:02:46 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 010078C060; Mon, 12 Jan 2009 12:02:45 -0600 (CST) Date: Mon, 12 Jan 2009 12:02:45 -0600 To: David Wolfskill Message-ID: <20090112180245.GA27132@soaustin.net> References: <20090112175707.GB5811@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090112175707.GB5811@albert.catwhisker.org> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-ports@freebsd.org Subject: Re: Is -j safe to use when building or updating ports? 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: Mon, 12 Jan 2009 18:02:46 -0000 Short answer: with the current infrastructure, it isn't. There is a WIP to fix this, but I dropped the ball in completing the review of it. The problem is dealing with the dependencies. mcl