Re: How do I cause standalone X11 apps to use MacPorts X11?
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 (/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 get these applications to recognize MacPorts' X11? I tried searching for existing advice and the most relevant-sounding thing I found was this: http://superuser.com/questions/459273/x11-and-mountain-lion-how-to-use-macports-xorg-server which suggested such mucking-about-with-system-files as sudo ln -s /opt/X11 /usr/X11. Is there a clean way to get these apps working? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How do I cause standalone X11 apps to use MacPorts X11?
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 game)), it opens the “X11 is no longer included with OS X” dialog. How do I get these applications to recognize MacPorts' X11? They're probably linking to stuff under /usr/X11 which is stubbed to produce that dialog. MacOSForge XQuartz installs a symlink from there to /opt/X11 to make such things work; a similar symlink to /opt/local might work (although it is a somewhat unfortunate solution, it seems to be how Apple expects it to be handled given XQuartz). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How do I cause standalone X11 apps to use MacPorts X11?
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 solution which fits into MacPorts's way of working. There isn't one, really; third party stuff is not expected to understand MacPorts. The only real alternative to the symlink is finding all the stuff in the 3rd party app and using install_name_tool to repoint it to MacPorts' X11; this may be problematic. (Indeed, it's entirely possible that you will run into problems with e.g. iconv with either the symlink or install_name_tool.) Perhaps the best solution for such third party programs is to bite the bullet and install XQuartz. You will need to reset the launchd stuff afterward if you want to keep using MacPorts' X11. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How do I cause standalone X11 apps to use MacPorts X11?
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 your MP prefix. I recommend starting with the XQuartz hook (which is installed on the system to setup the links to /opt/X11) and then just changing them to the MacPorts prefix (/opt/local in the example below): sudo port -v install xorg launchctl load -w /Library/LaunchAgents/org.macports.startx.plist sudo /usr/X11/libexec/xquartz_postinst.sh sudo rm /usr/X11 sudo rm /usr/X11R6 sudo ln -s /opt/local /usr/X11 sudo ln -s /opt/local /usr/X11R6 Note that loading the launchd.plist requires logout and login for $DISPLAY to propagate. --Jeremy ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: How do I cause standalone X11 apps to use MacPorts X11?
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 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 into MacPorts's way of working. What happens if you launch these apps from an xterm within MacPorts’ X11? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Octave 3.8.1 availability
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/mailman/listinfo/macports-users
Re: Octave 3.8.1 availability
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 that specific release); I haven't had time to update the patch to 3.8.0 or 3.8.1 ... there might be patch issues and/or build issues in doing so. I will hopefully get there before summertime, but I have a LOT on my queue right now that is higher priority. As always: If anybody wants to contract with me to get Octave 3.8 in place, I'm open to that arrangement. I'm also open to somebody else doing the work, posting diffs to the current Portfile and patchfiles, and then I'll test them and push them if they work. Otherwise, this will happen sooner or later, as my time allows. Sorry for the news. - MLD On Wed, Mar 26, 2014, at 05:29 PM, Jerry wrote: 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. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
