I believe this might be a possible "typo" in the ebuild. Currently, bind requires you to have mysql installed, actually when you have the mysql USE flag. I've switched to dev-db/mysql-bin but retain mysql in USE flags. No I cannot re-emerge bind. It seems the bind-mysql USE flag was invented just for this case and I believe it's not used by mistake in the ebuild.
Created attachment 58556 [details, diff] fix the ebuild
echo "dev-db/mysql-4.x.x" >> /etc/portage/profile/package.provided if you manage mysql outside of portage.
i've added mysql dependency for bind-mysql without ebuild bump and Jakub is right - you should add mysql entry into packages.provided since there is no mysql-bin ebuild in portage
Hmm, I used the mysql-bin experimental ebuild available in bugzilla #83424. To be honest, I just lost the ebuild as I've remerged portage tree and was yesterday lazy to put it into /usr/local/portage/ ... so at the moment portage doesn't know about mysql-bin, yes. But still I believe that when mysql-bin is released, the patch has to be applied anyway. Unless I miss the point of bind-mysql flag (but I've really just guessed what is the bind-mysql for).
bind-mysql is for mysql non-dlz support just emerge sync and try to emerge bind
Comment #4: Please, have a look at the ebuild and see what bind-mysql does. Or emerge gentoolkit: # euse -i bind-mysql local use flags (searching: bind-mysql) ************************************************************ [- ] bind-mysql (net-dns/bind): enables mysql support for bind (non-dlz)
please, reopen, if you think that problem is still exist and thanks for your attention. :-)
