Re: Tears and Wailing

2014-02-14 Thread Brandon Allbery
On Fri, Feb 14, 2014 at 9:41 PM, James Linder wrote: > > Brandon thanks so much for the help. Why xset -b is a problem I dunno, but > removing it from .profile fixed my issues with X11 not running. I have now > got the XQuartz dmg, not the macports version, dunno if that is significant > but all i

Re: Tears and Wailing

2014-02-14 Thread James Linder
On 15/02/2014 10:26 am, Brandon Allbery wrote: On Fri, Feb 14, 2014 at 9:19 PM, James Linder > wrote: I took this picture to show (on ps) XQuartz is running, gnuplot is running but there is no display. I'm stumped for ideas There's a "stuck" "xset b off" showing

Re: Tears and Wailing

2014-02-14 Thread Brandon Allbery
On Fri, Feb 14, 2014 at 8:42 PM, James Linder wrote: > So I bit the bullet and reinstalled maverics > > Now: > Everything worked ... > I tried to (including the dbus stuff) install gnome-terminal > No Error > gnome-terminal wont start > now NONE of the X11 things (gnuplot, xsane) will start > ht

Tears and Wailing

2014-02-14 Thread James Linder
Preamble: I had an iMac 27 running Snow Leopard with Macports - happy for years I wanted to do some android and ios stuff with Qt so I needed Qt5 which needs Mavericks I installed mavericks and all was good for a while but then eg gnome-terminal would not run I don't like mavericks spaces, their

Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript

2014-02-14 Thread Brandon Allbery
On Fri, Feb 14, 2014 at 12:56 PM, Gregory Shenaut wrote: > I've been reluctant to use anything under /opt because in the event I ever > need to scrub macports and start over, it's easier to remove /opt and > reinstall macports from scratch. > Other third party software uses /opt as well (and even

Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript

2014-02-14 Thread Ryan Schmidt
On Feb 14, 2014, at 11:56, Gregory Shenaut wrote: > On Feb 14, 2014, at 08:46 , Mark Anderson wrote: > >> I also install into /opt/ where expands to something >> descriptive of all the crap I am installing in there. Then I can turn PATHs >> on and off depending. This is really important for pl

Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript

2014-02-14 Thread Gregory Shenaut
On Feb 14, 2014, at 08:46 , Mark Anderson wrote: > I also install into /opt/ where expands to something > descriptive of all the crap I am installing in there. Then I can turn PATHs > on and off depending. This is really important for playing with things like > the gtk+ cocoa that needs its w

Re: mapserver with apache2 on Mavericks

2014-02-14 Thread Ryan Schmidt
On Feb 13, 2014, at 18:51, Nick Wharton wrote: > hmm.. "which apachectl" returns /usr/sbin/apachectl and it's not a softlink. > I believe it's the OSX default server. So i uninstalled the mapserver/apache2 > then: > sudo mv /usr/sbin/apachectl /usr/sbin/apachectl_original You should probably n

mapserver with apache2 on Mavericks

2014-02-14 Thread Nick Wharton
hmm.. "which apachectl" returns /usr/sbin/apachectl and it's not a softlink. I believe it's the OSX default server. So i uninstalled the mapserver/apache2 then renamed the apachectl: sudo mv /usr/sbin/apachectl /usr/sbin/apachectl_original then sudo port install mapserver +apache2 and run /opt/

Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript

2014-02-14 Thread Mark Anderson
I also install into /opt/ where expands to something descriptive of all the crap I am installing in there. Then I can turn PATHs on and off depending. This is really important for playing with things like the gtk+ cocoa that needs its whole space to itself. Just DONT use /opt or /opt/local of cour

Re: Problem with Macports, homebrew, and ghostscript

2014-02-14 Thread Sterling Smith
On Feb 13, 2014, at 8:07PM, asllearner wrote: > Sterling Smith wrote >>> According to >>> >>> https://trac.macports.org/wiki/FAQ#usrlocal >>> >>> you could try to rename /usr/local. MacPorts doesn't install anything to >>> /usr/local. If there is anything that stops working, then try to inst