MySQL error installing Drupal -- total serendipty -- side issue with macports install itself.

[Ryan Schmidt]

On Jan 14, 2010, at 13:07, William H. Magill wrote:

> 	 echo $PATH
> 	/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/Users/magill/bin:/usr/bin/X11:/usr/local/bin:/usr/local/sbin:/usr/local1/bin:/usr/X11R6/bin:/usr/bin/X11:/etc:/usr/etc:/usr/local/etc:/usr/local1/etc
> 
> So  I had to go back to see where THAT came from...
> 
> <--------- part of .profile ----------------->
> 
> ##
> # Your previous /Users/magill/.profile file was backed up as /Users/magill/.profile.macports-saved_2009-09-19_at_20:09:05
> ##
> 
> # MacPorts Installer addition on 2009-09-19_at_20:09:05: adding an appropriate PATH variable for use with MacPorts.
> export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> # Finished adapting your PATH environment variable for use with MacPorts.
> 
> 
> ##
> # Your previous /Users/magill/.profile file was backed up as /Users/magill/.profile.macports-saved_2009-10-13_at_16:36:02
> ##
> 
> # MacPorts Installer addition on 2009-10-13_at_16:36:02: adding an appropriate PATH variable for use with MacPorts.
> export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> # Finished adapting your PATH environment variable for use with MacPorts.
> 
> 
> ##
> # Your previous /Users/magill/.profile file was backed up as /Users/magill/.profile.macports-saved_2009-12-13_at_20:59:04
> ##
> 
> # MacPorts Installer addition on 2009-12-13_at_20:59:04: adding an appropriate PATH variable for use with MacPorts.
> export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> # Finished adapting your PATH environment variable for use with MacPorts.
> 
> <--------- end part of .profile ----------------->

The profile is only modified by the MacPorts dmg installer, and it is supposed to not modify the profile if it detects that it has already been modified. I don't know why this detection failed for you but I also don't have time to investigate it further right now. But you may want to file a bug report in the issue tracker because this should not be happening.