From owner-freebsd-ports@FreeBSD.ORG Wed Aug 2 04:33:04 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 F1CCD16A4DA for ; Wed, 2 Aug 2006 04:33:03 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52E7643D45 for ; Wed, 2 Aug 2006 04:33:03 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so512756nfc for ; Tue, 01 Aug 2006 21:33:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=c8ZHqJro7Hz5KT44+6f+q2NEvlD6Xb2Ro4+Q4H1GR+bVCVs/4Kzh5tdFln8OdxWlbgDmXw/XtkEnXUWhjja4wYGw6AMOLpTReN83pICg2F5JlfIBdVAJaF1DIfdd7p3CXoUbGlSeG656cYQIgiVkQE2WTrHm7uisE3xC+k4zKb8= Received: by 10.78.193.19 with SMTP id q19mr151927huf; Tue, 01 Aug 2006 21:33:02 -0700 (PDT) Received: by 10.78.83.2 with HTTP; Tue, 1 Aug 2006 21:33:02 -0700 (PDT) Message-ID: <790a9fff0608012133i52ed6e53t57a529d940fb2fa3@mail.gmail.com> Date: Tue, 1 Aug 2006 23:33:02 -0500 From: "Scot Hetzel" To: "Jeremy Messenger" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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 04:33:04 -0000 On 8/1/06, Jeremy Messenger wrote: > On Tue, 01 Aug 2006 22:50:30 -0500, Jiawei Ye wrote: > > > I am running into 2 problems. > > > > 1. Some ports want devel/bison as dependancy, I installed devel/bison2 > > and it works too. But when the bison1 depending port gets upgraded by > > portmaster, portmaster will insist on bringing in devel/bison, instead > > of devel/bison2. Not sure what the correct solution is. > > > > It is a known issue, I have reported to Doug a while back. I have a > workaround for it by hack in portmaster, but it is not a right solution. > Someone will have to figure a good solution. However, here's what I hacked > in portmaster. > : > 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. Looks like create a database is a better > solution? > How about changing the ports that depend on bison to use something like: USE_BISON= 1+ Then either submit a Mk/bsd.bison.mk file, or patch bsd.port.mk so that it will automatically detect which version of bison is installed (see USE_[MYSQL, POSTGRESQL, BDB] in Mk/bsd.databases.mk for an example) and added it as a BUILD_DEPENDS. Note: If a port also needs bison as a RUN_DEPENDS, you could use USE_BISON_RUN= 1+, and it would automatically set both a build, and run dependancy. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.