[MacPorts] #30678: mysql5 should not read /etc/my.cnf

[MacPorts]

#30678: mysql5 should not read /etc/my.cnf
-----------------------------------+----------------------------------------
 Reporter:  jeremyhu@…             |       Owner:  ryandesign@…           
     Type:  defect                 |      Status:  new                    
 Priority:  Normal                 |   Milestone:                         
Component:  ports                  |     Version:  2.0.1                  
 Keywords:                         |        Port:  mysql5                 
-----------------------------------+----------------------------------------

Comment(by jeremyhu@…):

 Replying to [comment:10 pixilla@…]:
 > Replying to [comment:9 jeremyhu@…]:
 > > What about editing the startup script to fail to start if
 ${prefix}/etc/my.cnf isn't present?
 > This would not be good. There is no documented requirement that ANY
 my.cnf exist.
 > > It can print a warning message that uses should create that file.  If
 someone really wants it to use /etc/my.cnf, they can comment that out or
 just use a symlink.
 > The mysql option files (my.cnf) are documented by the software authors.
 The MacPorts mysql5 port honors the mysql documentation.

 Right, well we have a problem in that if mysql-server is installed and not
 configured (as was my case because I install a ton of ports just to make
 sure they build and install), it can cause the server migration scripts to
 fail because it will result in MacPorts mysql "claiming" /var/mysql and
 the migration scripts will fail to migrate Apple's MySQL to that location
 from the previous system.

 How do you want to handle this?  I'm fine with it being documented on the
 upgrade page in the wiki if we don't want to actually change the software
 itself.

-- 
Ticket URL: <https://trac.macports.org/ticket/30678#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS