On May 16, 2013, at 9:59 PM, Ryan Schmidt <[email protected]> wrote:
> On May 16, 2013, at 23:33, Leo Singer wrote: > >> On May 16, 2013, at 9:29 PM, Jeremy Huddleston Sequoia wrote: >> >>> On May 16, 2013, at 8:45 PM, Leo Singer wrote: >>> >>>> Is it really just the patchfile >>>> https://trac.macports.org/browser/trunk/dports/x11/xinit/files/disable-launchagent.patch >>>> that disables on-demand loading of X11.app by default? >>> >>> Yes. >>> >>> This approach was taken because X11.app shipped before some Snow Leopard >>> 10.6.3 would not work correctly if $DISPLAY belonged to another server. >>> This is also why the XQuartz package requires 10.6.3 to install. >>> >>> It might be worth revisiting this and perhaps just disabling it on Leopard. >> >> Yes, please! It would be really nice if the MacPorts X11.app started >> automatically on Mountain Lion, without any further user intervention. > > I would rather work on the proposed extension of MacPorts startupitems to let > a port auto-load them; this would be useful for xorg-server, certsync, dbus, > etc. > > https://trac.macports.org/ticket/35474#comment:15 > > I agree that there should be an option to auto-load LaunchDaemons that are wrapped by startupitems, but I also think that the LaunchAgent should be on by default. They are separate issues. The startupitem handles the LaunchDaemon, not the LaunchAgent. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
