From owner-freebsd-ports@FreeBSD.ORG Mon Aug 7 19:33:12 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 436CE16A4ED for ; Mon, 7 Aug 2006 19:33:12 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.FreeBSD.org (Postfix) with SMTP id BE3E543D45 for ; Mon, 7 Aug 2006 19:33:10 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 27275 invoked by uid 399); 7 Aug 2006 19:33:10 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 Aug 2006 19:33:10 -0000 Message-ID: <44D79573.9080003@FreeBSD.org> Date: Mon, 07 Aug 2006 12:33:07 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: freebsd ports References: <44D0417C.8030405@FreeBSD.org> In-Reply-To: <44D0417C.8030405@FreeBSD.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jeremy Messenger , Jiawei Ye 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: Mon, 07 Aug 2006 19:33:12 -0000 Doug Barton wrote: > 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. Ok, I FINALLY got the new version (1.6) done, and committed. The good news is that the delay was caused by my finding more things to optimize. :) I have been giving some thought to your scenario, and while I still do not have an automated solution, I do have a workaround that will work from the command line. In the new version I enhanced the -i (interactive mode) feature to remember the user's choices made during the 'make config' recursive check so that you don't have to re-enter them at build time. So, let's say that you want to build build /usr/ports/foo/bar which has a dependency on bison, but you have bison2 installed. You would launch 'portmaster -i -p foo/bar' and when the dependency check got to bison, say no to building it. When the build for foo/bar starts, the ports tree will see that the bison dependency is filled by bison2, and not try to launch a build for it, and neither will portmaster. Like I said, it's not ideal or automated, but it does "fix" the problem while I work on the CONFLICTS idea you proposed (or some other solution if that doesn't work). hth, Doug -- This .signature sanitized for your protection