This might really depend on the application: is it checking for x11 or giving
up based on the OS?
On March 26, 2014 12:44:52 PM EDT, Kevin Reid kpr...@switchb.org wrote:
When I run X11 applications built by MacPorts, they open in the X11
server “app” built by MacPorts
On Wed, Mar 26, 2014 at 12:44 PM, Kevin Reid kpr...@switchb.org wrote:
When I run X11 applications built by MacPorts, they open in the X11 server
“app” built by MacPorts (/Applications/MacPorts/X11.app). When I run
separately distributed Mac-packaged X11 applications (MCEdit, Closure (the
On Wed, Mar 26, 2014 at 1:12 PM, Kevin Reid kpr...@switchb.org wrote:
It sounds like the assumption is that when you install third-party X11 as
instructed by the dialog, it will _replace_ the system-provided X11. But
MacPorts doesn't replace system files as a rule -- I'm looking for a
Instructions from the maintainer of MacPorts' xorg-server (from the -dev list):
On Mar 26, 2014, at 14:28, Jeremy Huddleston Sequoia jerem...@macports.org
wrote:
The stubs are there for projects that linked against /usr/X11. All you
really need to do is setup symlinks to redirect them to
On Wed, 26 Mar 2014, Kevin Reid wrote:
The dialog does not come from the application but from the system-provided
X11.app (this is observable by Dock/menu bar) which is a nonfunctional stub
(this is what my research says).
It sounds like the assumption is that when you install third-party
