Getting a second MacPorts into action FAILS

[Marko Käning]

> I don't think we should go changing the names of the plists.
> 
> Rather, it feels to me that dbus is in error to be installing these plists into /Library/Launch* even when startupitem_type is set to none, which it is in my secondary MacPorts installations. dbus is the only port (I know of) that has this issue, but probably other ports that manually install launchd plists will have it as well. These ports should check the startupitem type and not install the plists if it is none.

Should these plists instead rather be installed in the user's ~/Library/Launch* folders?

What is the startupitem_type you are writing about? I at least couldn't find this in the said plist files...