Uninstall of a port should automatically unload daemons

[tomldavis@…]

I'm developing on a port that starts a daemon using startupitem.executable. During installation, I get the standard message "A startup item has been generated ...". After I start the daemon with launchctl, everything works as expected.

However, if I uninstall the port without first manually unloading the daemon with launchctl, launchd repeatedly tries to restart the daemon (which of course no longer exists) every 10 seconds, ad infinitum.

This behavior (not automatically unloading daemons on uninstall) seems contrary to the MacPorts philosophy of a clean install/uninstall. This seems like a huge trap for the non-developer that doesn't have any idea of what launchd does and just wants to uninstall a port.

[ryandesign@…]

And when you upgrade a port that you've previously loaded, perhaps MacPorts should unload the old version's daemon and load the new one.

[ryandesign@…]

Resolving this would also close #14774 where this was previously brought up.

[rmstonecipher@…]

Cc Me!

[rmstonecipher@…]

On the other end of things, ports with startupitems usually work best when their startupitems are loaded.
If the port with a startupitem is several steps ahead of the user's requested port install, the "load the startupitem" note may be missed.
Could the user be cut out of this equation by auto-loading startupitems during the activate phase?
This would work for ports with startupitems which work as-is, but others may experience one or more of the following problems:

• some ports use both user- and system-level startupitems (e.g. dbus)
• some ports have configuration files that must be edited before running the daemon/startupitem
  

What other issues could auto-loading startupitems cause?

Ryan Stonecipher