I just switched to bind912 and noticed that poudriere still builds bind911 in addition to bind912. This is because I have the DNS_BIND911 option set in net-mgmt/nagios-plugins. The patch adds DNS_BIND912, DNS_BIND913, and DNS_BIND914 options. This resulted in a lot of duplicate --with-dig-command and --with-nslookup-command CONFIGURE_ARGS so replaced them with a .for look that adds the appropriate --with-*-command configure args.
I also moved CONFLICTS_INSTALL after USES to make portlint happier.
Created attachment 202527 [details]
It occurs to me that another way to solve this would be to create a dns/bind master port (similar to www/py-django) and use it to pick the version of bind. Ports that want to use some ports version of bind (e.g. net-mgmt/nagios-plugins) could depend on dns/bind.
Let me know if you'd like to see a patch that does this.
Well, as www/py-django must not be depended upon (a bit like lang/python or lang/gcc), having a dns/bind9 port would not help a bit in this case.
Also, I ignored your patch as it would have used dig from ports even if the user had chosen to use base systems tools. (say if any bind port is already installed.)
A commit references this bug:
Date: Tue Mar 12 16:11:15 UTC 2019
New revision: 495467
Add BIND9 9.12 and 9.14 as possible depends.
Reported by: leres
(In reply to Mathieu Arnold from comment #4)
I meant to comment on this earlier; your fix (using BIND_VERS) is much slicker, thanks!