All, I took over maintainership of p5-DBD-mysql last week. Apparently I unwittingly managed to poke a hornets nest. Upstream author changed the code to make it only compatible with MySQL 8.x. I've tried patching out some of those changes but it requires quite an effort and is, in the end, unmaintainable. So currently it is broken if you change the default mysql to MariaDB.
At the moment I see a couple of options 1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql4 'legacy' version port. 2) 'downgrade' p5-DBD-mysql to 4.051 and add a p5-DBD-mysql5 'new' version port. #1 works for the default MySQL (still at 8.0) but breaks if trying to build with MariaDB. Arguments are made that those ports should switch to p5-DBD-mariadb instead. But this causes another set of problems, it's not a drop-in replacement and some ports seem to have problems with DBD-MariaDB. Those ports could switch to the 'legacy' version until those issues are resolved upstream. #1 also poses a problem if the default is switched to MariaDB and ports haven't been updated yet to depend on p5-DBD-mariadb or p5-DBD-mysql4. #2 is probably the 'quickest' fix, it restores the status quo. Ports could include p5-DBD-mysql5 if they have a requirement for the new version (and add a restriction to only build with MySQL 8.x). While typing this out, trying to get some advice, I'm inclined to go for #2. But how can I go back a version? Bump PORTEPOCH? Sorry for the noise this caused. It wasn't intended. Greetings, Remko C. aka SirDice
