/usr/bin/mysql_setpermission is part of the mysql ebuild. It uses perl's DBI module, but no dependency for dev-perl/DBI is defined. I found this bug in mysql-3.23.54a.ebuild but haven' tried earlier versions of mysql. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Maybe it would be a good idea to only include this tool if USE="perl" is defined?
Thats not a _general_ solution. "perl" is one of my USE flags, but the DBI module isn't emerged on my system. Checking that flag would only help in situations where a user doesn't want perl at all.
I think there are only two cases: either installing MySQL causes DBI to be installed, or mysql_setpermission is not included in the installed files. I was suggesting that the dependency on DBI be made specific to cases where USE="perl" is defined, reasoning that people with USE="-perl" would be rather upset to discover that they could not install MySQL without bringing Perl in, and would instead be happier with mysql_setpermission not existing.
fully agreed
well i was going to fix this by making DBI and DBD-Mysql a PDEPEND since mysql has to be installed to compile dbd-mysql, go ahead and do this if you want rac, this is the correct solution i think
I was thinking it would be nice to have that PDEPEND be conditional on whether USE="perl" was defined - that way people that don't want perl don't get perl modules they would not want.
Fixed in 3.23.54a-r1.
