/opt/local/mysql path?

[dweber@…]

Just curious, I wonder why macports installs mysql5 below /opt/local/lib rather than a similar default to /usr/local/mysql (perhaps /opt/local/mysql, as in /opt/local/apache2).

/opt/local/lib/mysql5/bin:
comp_err*                    mysql_waitpid*
innochecksum*                mysql_zap*
msql2mysql*                  mysqlaccess*
my_print_defaults*           mysqladmin*
myisam_ftdump*               mysqlbinlog*
myisamchk*                   mysqlbug*
myisamlog*                   mysqlcheck*
myisampack*                  mysqld_multi*
mysql*                       mysqld_safe*
mysql_client_test*           mysqldump*
mysql_config*                mysqldumpslow*
mysql_convert_table_format*  mysqlhotcopy*
mysql_explain_log*           mysqlimport*
mysql_find_rows*             mysqlshow*
mysql_fix_extensions*        mysqltest*
mysql_fix_privilege_tables*  mysqltestmanager*
mysql_install_db*            mysqltestmanager-pwgen*
mysql_secure_installation*   mysqltestmanagerc*
mysql_setpermission*         perror*
mysql_tableinfo*             replace*
mysql_tzinfo_to_sql*         resolve_stack_dump*
mysql_upgrade*               resolveip*
mysql_upgrade_shell*

/opt/local/lib/mysql5/mysql:
libdbug.a                     libmysqlclient_r.15.0.0.dylib*
libheap.a                     libmysqlclient_r.15.dylib@
libmyisam.a                   libmysqlclient_r.a
libmyisammrg.a                libmysqlclient_r.dylib@
libmysqlclient.15.0.0.dylib*  libmysqlclient_r.la*
libmysqlclient.15.dylib@      libmystrings.a
libmysqlclient.a              libmysys.a
libmysqlclient.dylib@         libvio.a
libmysqlclient.la*

Take care, Darren

PS, I figured a ticket would help document the rationale for this better than an email to macports-users.

PPS, A similar rationale has been adopted for postgresql too, but not for apache2. I haven't found anything on this in the FAQ, so please point me to a manifesto, if it exists?

[ryandesign@…]

​A recent discussion on the list complained about apache2 violating the mtree and asked why its contents wasn't better integrated into the existing tree. I believe the answer was that nobody had gone to the effort. So we should be striving to make things conform with the MacPorts tree (convert apache2 to be more like mysql5), and not put things into their own little prefixes under the MacPorts prefix (we should not convert mysql5 to be more like apache2).

Note that the mysql5 layout could still use some improvement. It's a bit weird in places.

[anonymous]

Milestone Port Enhancements deleted