Re: Octave 3.8.1 availability

2014-03-26 Thread Michael Dickens
Hi Jerry - There is a ticket open discussing reincarnating octave-devel as the 3.8 release series: < https://trac.macports.org/ticket/41155 >. I haven't had time to do more than post a patch for folks interested in trying this change out. The patch provides 3.8.0-rc1 (along with patchfiles for th

Octave 3.8.1 availability

2014-03-26 Thread Jerry
Does anyone have any idea when Octave 3.8.1 will become available? It's been out for several weeks and as of 3.8 includes a beta version of the GUI. Jerry ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/m

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Brandon Allbery
On Wed, Mar 26, 2014 at 2:48 PM, Ludwig wrote: > What happens if you launch these apps from an xterm within MacPorts’ X11? > This won't help; it's the client libraries that are stubbed in this case, and xterm does not control those. -- brandon s allbery kf8nh sine

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Ludwig
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-par

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Jeremy Lavergne
Instructions from the maintainer of MacPorts' xorg-server (from the -dev list): On Mar 26, 2014, at 14:28, Jeremy Huddleston Sequoia 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 your MP prefix. I >

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Brandon Allbery
On Wed, Mar 26, 2014 at 1:12 PM, Kevin Reid 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 > solution which fits in

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Brandon Allbery
On Wed, Mar 26, 2014 at 12:44 PM, Kevin Reid 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 > game)), it opens t

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Kevin Reid
On Mar 26, 2014, at 10:07, Jeremy Lavergne wrote: > This might really depend on the application: is it checking for x11 or giving > up based on the OS? 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 nonfunctio

Re: How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Jeremy Lavergne
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 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 >ru

How do I cause standalone X11 apps to use MacPorts X11?

2014-03-26 Thread Kevin Reid
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 game)), it opens the “X11 is no longer included with OS X” dialog. How do I