#39129: xinit: X11.app does not start automatically on Mountain Lion --------------------------+------------------------ Reporter: aronnax@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: haspatch Port: xinit | --------------------------+------------------------ Comment (by jeremyhu@…): Replying to [comment:3 aronnax@…]:
Replying to [comment:1 jeremyhu@…]:
I think we should stop providing the LaunchAgent in the xinit port and instead provide it in the xorg-server and xorg-server-devel ports.
Note that I'm not opposed to this current patch being an intermediate step towards that end. I don't have much time to dedicate to this at the moment. Feel free to commit if you don't want to do the change that I suggested.
Sounds fine to me, but:
What depends on {{{xinit}}}? On my machine I see only: {{{ $ port dependents xinit xorg-apps depends on xinit xorg-server depends on xinit }}}
Why does {{{xorg-apps}}} depend on {{{xinit}}}?
Legacy reasons that probably don't matter much any more. That is from when we made the xorg-apps, xorg-libs, and xorg meta ports to help ease transition.
Perhaps this question just exposes my ignorance of X11's architecture. If {{{xinit}}} was only a dependency of {{{xorg-server}}}, then I would say that it might be OK to have {{{xinit}}} provide the LaunchAgent.
I want to protect against users that have xinit without xorg-server. This is most likely to happen if they hit an error that prevents xorg-server from installing after xinit has been activated. -- Ticket URL: <https://trac.macports.org/ticket/39129#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X