If I would install only postgresql client libraries then I need to install: dev-db/postgresql[-server] when I'd like to have only mysql client library I need to install: dev-db/mysql[minimal] Could be the USE flags unified? "minimal" isn't informative for me, I prefer "server" USE flag. So I would like to see dev-db/mysql[server] and dev-db/postgresql[server]. Reproducible: Always
> So I would like to see dev-db/mysql[server] and dev-db/postgresql[server]. +1
I actually have thoughts to do the opposite but still could rename the minimal flag if you really want it. I may either have to: 1) create a virtual/libmysqlclient with the mysql-connector-c (currently only in mysql overlay) as the primary library to link to and the servers never, or via a client-libs USE, install the libraries. Minimal, or -server, would be simple tools 2) Wait for mariadb to catch up to dev-db/mysql with so.20. This would mean delaying MySQL 5.7 until (probably) MariaDB 10.2.x
(In reply to Brian Evans from comment #2) > I actually have thoughts to do the opposite but still could rename the > minimal flag if you really want it. In our case for PostgreSQL, "minimal" would not be representative of reality. The difference between client-only and server is, effectively, whether or not the server binary is created. The bulk of the work in the libs. (So, even compiling libs only would only save 2 or 3 minutes out of 15 on my machine.) I have no idea what it's like on MySQL's side.
USE="server" introduced on the mysql, and derivatives, server packages in ~arch first
