On Feb 24, 2008, at 19:12, Mark Hattam wrote: > The problem is that if you do miss these messages, then you can't > easily resurrect them other than installing the whole lot again.
True-ish. Well really you only need to deactivate and active the port again, since ports print such messages in the post-activate phase. But users don't know that. You could also read the portfile source code, but that's not really a clean solution either. Any suggestions for how we could improve this situation? > And sometimes you seem to need to run the same MySQL launch command > after updating MySQL and other times not. If the port is "loaded" (that is, you've run "sudo launchctl load -w / Library/LaunchDaemons/org.macports.whatever.plist") then the plist file is changed to indicate that the plist should be loaded at startup. If you now upgrade the port, the old plist is uninstalled, and a new plist is installed, and the new plist contains the usual MacPorts defaults, including that the plist should not be loaded at startup. This means (the old version of) the software is still running, but there's no way to stop it, because running "sudo launchctl unload -w / Library/LaunchDaemons/org.macports.apache2.plist" will claim the plist is already unloaded. And so there's no way to start the new version of the software. You really have to unload the plist before upgrading the port, then load the plist after upgrading. Now that we have "port load" and "port unload" as shortcuts for "sudo launchctl load" and "sudo launchctl unload", maybe port should automatically unload a port before deactivating, and then, if the port was previously loaded, load the port again after activating. I should finally file a bug about this. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
