virtual/mysql-5.6-r8 was changed from virtual/mysql-5.6-r7 to now require a mysql server on the current system. While this corresponds to the description of the virtual "Virtual for MySQL database server", there are clearly client-only ebuilds such as dev-perl/DBD-mysql-4.32.0-r1 and net-analyzer/monitoring-plugins-2.1.2[mysql] which depend upon virtual/mysql. Even mariadb[-server] currently ends up depending upon virtual/mysql through mysql-multilib-r1.eclass. This obviously is not a problem on systems with USE=server set on mysql or mariadb, or percona-server, but leads to clashes on client machines where mysql or mariadb is installed with -server. So I guess we can either continue with the lenient definition of virtual/mysql-5.6-r7, which made no assumptions on the server use flag of other packages, or add a "server" use flag to virtual/mysql as well (and probably in any case change the description to "Virtual for MySQL database"). Best regards, Bernd
If an ebuild requires the client libraries, it should depend on virtual/libmysqlclient. This was created almost a year ago so that virtual/mysql would be the server virtual. I'll make an announcement on the developer list to get some push going. Creating bugs here is also appropriate including a tracker. I don't have the time to walk though every package personally though.
