need mysql_select or different approach to solve mysql woes

[nefar@…]

is there a mysql_select ? I keep running into issues with mysql, and it's really hard to set up to get it running.

For example, my error log tells me to run mysql_ugprade. When I run it, I get

[~]$ mysql_upgrade5 
Looking for 'mysql' as: mysql                                                                       
FATAL ERROR: Can't execute 'mysql'

Of course, none of the files are symlnked properly, and mysql doesn't seem to be aware of this.

It seems to me the correct way to label the binaries should be using the

--program-prefix

flag

[ryandesign (Ryan Carsten Schmidt)]

Replying to nefar@…:

is there a mysql_select ?

Duplicate of #29907.

[~]$ mysql_upgrade5
Looking for 'mysql' as: mysql
FATAL ERROR: Can't execute 'mysql'

Duplicate of #20949.

It seems to me the correct way to label the binaries should be using the

--program-prefix

flag

There is a comment in the port that's been there for a long time (since r59788) saying use of that flag is in store for the future. This was ported to the mysql5 port from the mysql5-devel port, where this option had been used, but was removed in r30318 because according to #12954 it was broken. The two referenced upstream bug reports about it are still not resolved. ​MySQL bug 11913 has not been touched in two years, and ​MySQL bug 25226 was closed as wontfix saying they can't support this option. The current version of MySQL 5.5 (not yet in MacPorts but will be once I resolve #25751) has switched to cmake so I don't know if that changes the situation at all.

The workaround for you for now is put /opt/local/lib/mysql5/bin in your PATH.

[nefar@…]

thanks for pointing out the workaround