Date: Tue, 01 Aug 2006 23:09:00 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Jeremy Messenger <mezz7@cox.net> Cc: Jiawei Ye <leafy7382@gmail.com>, freebsd ports <freebsd-ports@freebsd.org> Subject: Re: portmaster, bison, java/jdk15 Message-ID: <44D0417C.8030405@FreeBSD.org> In-Reply-To: <op.tdm2bak89aq2h7@mezz.mezzweb.com> References: <c21e92e20608012050i4721f83er5d5a6c83e54d754@mail.gmail.com> <op.tdm2bak89aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D0417C.8030405>