From owner-freebsd-ports@FreeBSD.ORG Wed Aug 2 06:09:08 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A88A316A4E0 for ; Wed, 2 Aug 2006 06:09:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 283FB43D4C for ; Wed, 2 Aug 2006 06:09:07 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 26306 invoked by uid 399); 2 Aug 2006 06:09:05 -0000 Received: from localhost (HELO ?192.168.0.9?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 2 Aug 2006 06:09:05 -0000 Message-ID: <44D0417C.8030405@FreeBSD.org> Date: Tue, 01 Aug 2006 23:09:00 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Jeremy Messenger References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jiawei Ye , freebsd ports Subject: Re: portmaster, bison, java/jdk15 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: Wed, 02 Aug 2006 06:09:08 -0000 Jeremy Messenger wrote: > It is a known issue, I have reported to Doug a while back. *nod* > As for solution, right now I am thinking about check on each port's > conflict. Like for example: > > - Check on if devel/bison has any of CONFLICT. > - CONFLICTS is devel/bison2, then check if > devel/bison2 exists. > - devel/bison2 does exist, then remove the > devel/bison out of dependency check list. > - Check if devel/bison2 needs to update. > - [...goes on as normal...] > > I don't know if it's good idea. That is a good idea, thanks for suggesting it. I will look at some code to do that, although I might not get it into the current version, as I'm almost done with some serious performance optimizations that I'd like to get out the door. > Looks like create a database is a better solution? Heh, no. Doug -- This .signature sanitized for your protection