# emerge -pv mod_log_sql
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] dev-db/mysql-4.0.24 +berkdb -debug -innodb +perl +readline (-selinux) +ssl -static +tcpd 16,489 kB
[ebuild N ] net-www/mod_log_sql-1.97 145 kB
[ebuild N ] dev-perl/Net-Daemon-0.37 29 kB
[ebuild N ] dev-perl/Storable-2.13 131 kB
[ebuild N ] dev-perl/PlRPC-0.2016-r1 17 kB
[ebuild N ] dev-perl/DBI-1.38-r1 292 kB
[ebuild N ] dev-perl/DBD-mysql-2.1027 95 kB
I'm wanting to log to a remote MySQL server; therefore, there's no need in MySQL being install locally.
Steps to Reproduce:
MySQL should not be a dependency of mod_log_sql
mod_log_sql documentation clearly states that remote logging to a MySQL server
is possible: http://www.outoforder.cc/projects/apache/mod_log_sql/docs-2.0/
Never installed/used mod_log_sql but probably it need at least mysql libraryes and header files.
If you don't need the -server- emerge =dev-db/mysql-4.0.24-r1 with the "minimal" USE flag (new option), this install only the environment needed by a -client- mysql installation.
In fact unless you want to use odbc you need something that connect to a MySQL server.
I'm certainly not saying you're wrong, but, unless I'm missing something, the install docs don't say anything about needing MySQL locally.
you need mysql header and library files to compile mod_log_sql
anyways, you can open a bug report requesting a split of mysql to mysql-server and libmysqlclient or alike in order to explicitely fix such behaviors. though, packages like mod_log_sql (and others) could just depend on the client library. If this 's gonna be accepted, than we'll update mod_log_sql to depend on this lib only.
btw, I'd appreciate such a solution.
As a result of the new bug 88490 as a request for mysql ebuild split, I reopen this one to get fixed ASAP #88490 is done.
mysql maintainers won't split that package, and I'm fairly sure mod_log_sql
needs at least the client libs. CANTFIX
"USE=minimal emerge mysql" and then you can do emerge mod_log_sql fine.