portmaster, bison, java/jdk15
swhetzel at gmail.com
Wed Aug 2 04:33:04 UTC 2006
On 8/1/06, Jeremy Messenger <mezz7 at cox.net> wrote:
> On Tue, 01 Aug 2006 22:50:30 -0500, Jiawei Ye <leafy7382 at gmail.com> 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
How about changing the ports that depend on bison to use something like:
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
No electrons were mamed while sending this message. Only slightly bruised.
More information about the freebsd-ports