Re: Problem with Macports, homebrew, and ghostscript
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 install it from MacPorts instead. For instance: port search lyx ... Found 2 ports. port search latex ... Found 34 ports. Also note that texlive is broken into smaller pieces http://trac.macports.org/wiki/TeXLivePackages Hope that helps, Sterling I am sorry, I don't understand. Try to move usr/local to what end? Before, after, or instead of removing brew. The link talks about temporarily renaming usr/local while installing ports, i.e. if installation of a port runs into conflicts with usr/local. That is not quite my problem... From what I understood of your problem, you had programs that were undesirably being run or linked from /usr/local . By renaming it, you can most likely remove that problem. If brew has uninstallation procedures, then I would use them first, in case brew puts things in other places besides /usr/local. Then after uninstalling brew, rename the folder. As you continue to work, you may notice that certain programs/libraries are not available anymore; when you run across them, see if they are in macports, and install them from there. If they are not in macports, then you can file a ticket to create a new port. -Sterling ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript
I also install into /opt/something where something 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 course. I also set them to be owned by my user, so I don't have to sudo to install. If I do, I know something is up. Mark --Mark ___ Mark E. Anderson e...@emer.net On Wed, Feb 12, 2014 at 10:56 AM, Arno Hautala a...@alum.wpi.edu wrote: On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut gkshen...@ucdavis.edu wrote: I understand why installing in /usr/local can mess up macports, but macports doesn't have everything, and most third-party software wants to go into /usr/local. Where should this stuff go, if not /usr/local? I install everything into my home folder. ./configure --prefix=~/local/ make make install If you need it available system-wide, just pick some other custom location (ie. /custom/). In any case, just make sure you're consistent (update your PATH) and point your configure script to the right place if the software can't find the libraries in your path or you need to override libraries that are in your path. The longer answer is that I use stow (http://www.gnu.org/software/stow/ ; and available in MacPorts) to assemble the bin, man, etc. directories. Stow isn't required, but it does help manage the software that isn't being managed by MacPorts. So, I might install a piece of software with: ./configure --prefix=~/local/stow/foo-1.2.4 make make install cd ~/local/stow stow foo-1.2.4 Stow just allows you to easily add and remove versions of software by linking a hiearchy of directories into a common location. I might have foo-1.2.4, foo-1.2.6, bar-3.9, but only have foo-1.2.4 and bar-3.9 active. I can the upgrade to foo-1.2.6 by running: cd ~/local/stow stow -D foo-1.2.4 stow foo-1.2.6 rm -rf foo-1.2.4 -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9d448 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
mapserver with apache2 on Mavericks
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/local/apache2/bin/apachectl start (after changing ServerName). This time the right apache starts and the logs are updated. If i enter http://localhost/cgi-bin/mapserv it returns an error and the following is in the error_log: /opt/local/apache2/cgi-bin/mapserv: error: `/opt/local/apache2/cgi-bin/.libs/mapserv' does not exist There is a /opt/local/bin/mapserv, though. Should i modify the script to point to this directory? thanks! ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: mapserver with apache2 on Mavericks
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 not modify Apple-provided software. But you’re right, /usr/sbin/apachectl is for Apple’s apache, so you won’t be using that if you’re interested in controlling MacPorts apache. then sudo port install mapserver +apache2 and run /opt/local/apache2/bin/apachectl start (after changing ServerName). This time the right apache starts and the logs are updated. If i enter http://localhost/cgi-bin/mapserv it returns an error and the following is in the error_log: /opt/local/apache2/cgi-bin/mapserv: error: `/opt/local/apache2/cgi-bin/.libs/mapserv' does not exist Hmm. I’ll have to install the port myself and see if I can reproduce that problem. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript
On Feb 14, 2014, at 08:46 , Mark Anderson e...@emer.net wrote: I also install into /opt/something where something 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 course. I also set them to be owned by my user, so I don't have to sudo to install. If I do, I know something is up. 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. I'm currently installing all my own programs scripts in my home directory, with traditionally named folders like bin, doc, include, lib, libexec, man, share, src, var, and tmp. There are a few downloaded apps there too, but there are also a few where it seemed like too much work to keep them from going right into /usr/local where they belong. For a while, I had a separate sub-hierarchy in my home directory, with a symlink in / pointing to it; that way, I could refer to things I installed as /whatever/... and so on, as an alternative to ~/whatever/... But I decided that since I'm the only one that uses my Mac, I was just being compulsively traditional in making those things accessible from the root. It's a pity that macports isn't an official part of the system, like the freebsd ports are in fbsd, because if it were, then they (and not other ports) could simply install things right into the main system hierarchy. I believe that historically, really core elements of the OS went into /bin /lib and so on (this was back in the days when the root volume couldn't be very large), where “extra” things of interest to users things went into /usr/bin /usr/lib and so on (sometimes these were each on different physical drives). Locally-written things went into /usr/local, also often on a separate drive. When Berkeley started distributing their collections of software, they used /usr/ucb to keep it separate. For most unixy systems, that's really all you need, because an official ports system can then install things wherever they like without messing themselves up. But on the Mac, since there never has been an official ports system, there is competition between standard utilities wanting to be installed in /usr/local and several different ports systems. As a result we have /opt /sw and so on (I have no idea why the original pattern of /usr/ucb wasn't followed with /usr/mp, /usr/fink, and so on, but it wasn't), as well as a host of troubles when the assumptions of the various ports systems are violated. I suppose that's just another word for freedom. What I'm seeing from these responses is basically what I had always assumed, namely that macports doesn't really care where you install other software, as long as it isn't in /opt (or perhaps only /opt/local). Greg Shenaut ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript
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/something where something 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 course. I also set them to be owned by my user, so I don't have to sudo to install. If I do, I know something is up. 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. Feel free to install anything you like in prefix /opt/anything-other-than-local. That’s a great and standardized location for random other software to go that won’t interfere with MacPorts. The default MacPorts prefix is /opt/local. If you need to uninstall MacPorts, you can follow our uninstallation instructions, which will have you removing /opt/local and a few other paths, but not /opt/anything-other-than-local. What I'm seeing from these responses is basically what I had always assumed, namely that macports doesn't really care where you install other software, as long as it isn't in /opt (or perhaps only /opt/local). If you want to install random other software while also using MacPorts, I suggest you install that other software into a prefix that is not any of the following: * /usr * /usr/local * /opt/local * your MacPorts prefix (if different from /opt/local) * /sw And also avoid installing frameworks into /Library/Frameworks and of course /System/Library/Frameworks. I think that’s about it. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Where should non-macports sw be installed? (Was: Problem with Macports, homebrew, and ghostscript
On Fri, Feb 14, 2014 at 12:56 PM, Gregory Shenaut gkshen...@ucdavis.eduwrote: 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 some Apple software; see xquartz). /opt/local is the only part that MacPorts touches; the rest of /opt is (and is there to be) fair game. It's a pity that macports isn't an official part of the system, like the freebsd ports are in fbsd, because if it were, then they (and not other ports) could simply install things right into the main system hierarchy. I believe that historically, really core elements of the OS went into /bin /lib This is a nightmare when installing newer versions of OS-provided things and when trying to keep base system and add-ons separate. Linux likes to pretend this is not a problem but its package managers are not really good enough to deliver on their claims; this often manifests as system upgrade failures. systems. As a result we have /opt /sw and so on (I have no idea why the original pattern of /usr/ucb wasn't followed with /usr/mp, /usr/fink, and so on, but it wasn't), as well as a host of /usr is often read-only on BSD-derived systems (while the relationship is now rather distant and I think OS X can't actually get away with r/o /usr, it is nevertheless BSD-derived and userspace is synced somewhat regularly with FreeBSD-CURRENT). /usr/ucb made sense in the original BSD context since it was populated as part of an OS install and could be considered read only afterward, plus you still had the original ATT versions of utilities available when needed for portability; aftermarket stuff doesn't really belong there (if you're remounting /usr r/w constantly to add software, you're doing read-only wrong) /opt originated on Solaris, in part to support read-only (or shared; consider zones) /usr, but it seems like everyone else has come up with their own justification for it. -- 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
Tears and Wailing
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 mail (thanks for comments Ryan, but it is still not right), also my linux boxen and mavericks would not play together with printing (much spelunking and CUPS fiddling). So I reinstalled snowleopard but the certificates for xcode have expired 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 I removed macports and all trace of macport files as per the docs I reinstalled mackports and built gnuplot, xorg-server, wget, xsane both xsane and gnuplot just hang (yes I did log out) Short of clutch dagga between teeth and climb to top of tower can anybody lend me a suggestion please. PS qt apps build and display without issue and mythfrontend works fine too. (I thought that they did use X11) James ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tears and Wailing
On Fri, Feb 14, 2014 at 8:42 PM, James Linder j...@tigger.ws 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 http://xquartz.macosforge.org ? (or see the xinit port to configure xquartz via macports instead) PS qt apps build and display without issue and mythfrontend works fine too. (I thought that they did use X11) I thought qt4-x11 had been purged because of severe bitrot. qt4-mac is Aqua, not 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: Tears and Wailing
On Fri, Feb 14, 2014 at 9:41 PM, James Linder j...@tigger.ws 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 is working .profile?! That'd be bad, yes, since it's getting run as part of the setup for X server startup, and the xset causes X server startup, which runs xset, which tries to start the X server, ... see the problem? If you want to run it during X startup, create an executable script ~/.xinitrc.d/99xset.sh: #! /bin/sh xset -b -- 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
