Getting a second MacPorts into action FAILS

Marko Käning MK-MacPorts at techno.ms
Sat Oct 23 06:24:22 PDT 2010


This
> ---
> --->  Staging dbus into destroot
> --->  Installing dbus @1.2.24_1
> --->  Activating dbus @1.2.24_1
> Error: Target org.macports.activate returned: Image error: /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and does not belong to a registered port.  Unable to activate port dbus. Use 'port -f activate dbus' to force the activation.
> Log for dbus is at: /opt/macports-test/var/macports/logs/_opt_macports-test_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/main.log
> Error: Status 1 encountered during processing.
> ---
is all not necessary, since as one can see those services are normally not started:
---
$ launchctl list | grep dbus
$
---

But even if they get started one could avoid this trouble by including the MacPorts prefix in the plist's file name like this for instance:

 /Library/Lauch(Agents|Daemons)/org.freedesktop.dbus-session.opt.local.plist
 /Library/Lauch(Agents|Daemons)/org.freedesktop.dbus-session.opt.macports-test.plist

Then there would be no confusion about as to which dbus.plist one should symlink to.

How about this, Michael? Anything against this approach?


More information about the macports-dev mailing list