MAMP issue -- Mysql 56

[Ryan Schmidt]

On Dec 26, 2014, at 5:27 AM, William H. Magill wrote:
> 
> I know next to nothing about the installation of MySQL, so I need some serious direction here.
> 
> In installing MySQL 56 via MacPorts, I find that the instructions imbedded directly in the port file differ materially from those on the MAMP page written for MySQL 51.
> https://trac.macports.org/wiki/howto/MAMP
> 
> Once the install completes, the next instruction on the MAMP page states:
> 
> # sudo -u _mysql mysql_install_db5
> 
> That is easily fixed by running the install program as installed by the port: mysql_install_db

The old mysql5 port installed both mysql_install_db in a deep directory, and a symlink mysql_install_db5 pointing to it. The new MySQL ports (mysql51, mysql55, mysql56, mariadb, mariadb-10.0, mariadb-10.1, percona) only install mysql_install_db in the deep directory.



> At the end of that execution, the following information is printed:
> 
> ==========<cut here>================
> To start mysqld at boot time you have to copy
> support-files/mysql.server to the right place for your system

> 1- the files referenced in the first instruction above are not identified -- neither their source location nor their destination.
> One guesses that the source files is: /opt/local/share/mysql56/support-files/mysql.server
> However, that file appears to be a generic start file -- which only needs modification if one does NOT use /opt/local.
> But there is no indication of WHERE the "right place" is for a MacPorts installation.
> If nothing needs to be done, a statement to that effect needs to be in MAMP

The mysql.server file is not applicable on OS X. On OS X we use launchd plists instead. In MacPorts launchd plists and other relevant server extras are provided in companion -server ports, e.g. mysql56-server.

The message to do something with that file comes from MySQL's installation script, not MacPorts.


> WARNING: Could not copy config file template /opt/local/share/mysql56/support-files/my-default.cnf to
> /opt/local/etc/mysql56/my-new.cnf, may not have access rights to do so.
> You may want to copy the file manually, or create your own,
> it will then be used by default by the server when you start it.
> ==========<cut here>================

> 2- it appears that instructions to change the ownership/write permissions of /opt/local/etc/mysql56/ need to be included
> for the "my-new.cnf" file or instructions to replace the "my.cnf" file included.
> However, the chown instructions on the MAMP page appear to no longer be necessary.


I've never been satisfied with the way the MAMP page says to do some steps, then do some other steps if the first steps didn't work, with no explanation as to the circumstances under which the first steps are expected not to work; nobody has ever explained to me why those instructions are in that page. I really dislike the MAMP page entirely and wish it would be replaced with simple individual pages for each software package.