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
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
