If you're trying to use multiple package managers to maintain complex development and server environments, though, you're probably in a for a world of discomfort at least. I've run into very few difficulties this way, even before learning the port -t trick.
Uninstall macports el capitan install#
To be honest, I run with Fink, MacPorts and Homebrew all at once, with deference to MacPorts (for now anyway), and only using either of the other two to install things I can't get from MacPorts. I'll just note how much worse packaging is on OSX than FreeBSD: Apple does not really seem to care about the usability of its BSD subsytem, because this is a problem they could help with. And once you realise that problems in /usr/local do not generally carry the risk of permanent damage to your machines, you may feel freer to take risks. If you are willing to document which packages you need with Homebrew, and wipe /usr/local clean and reinstall in case of difficulties, then you can always back out in the case things go badly wrong. Homebrew, in this respect at least, does things the way they used to be done, and MacPorts tries not to interfere. I understand that the motivation is to make life easier for themselves when dealing with cries for help on their mailing list and bug tracker: please be aware, though, that while we should respect the effort of volunteer packagers and treat their time as precious, their debugging convenience is not the only sort of simplicity that affects you, as a user. I tried configuring MacPorts to install to /usr/local, but MacPorts goes out of its way to make that difficult. Since my experience with MacPorts and Fink has typically been exasperation caused by exactly this, and at some point switching to compiling the old-fashioned way to /usr/local, I was pleased to see that Homebrew didn't mess about with that. But while Autoconf usually does figure out issues, the sheer build complexity of many open-source projects does cause problems and these problems can be hard to back out of when you get into difficulty.īut the risk of trouble with Autoconf finding something it shouldn't under /usr/local needs to be balanced about the maintenance nuisance having two, three, or four different different copies of Perl, Tcl, and Ruby, each with different coverage of their different package libraries. The build tools expect there to be lots of things there: in the good old days before package managers (I joke), we compiled whatever to /usr/local.
Uninstall macports el capitan manual#
See this answer over on Ask Different for more info.įinally, each port installed through MacPorts may again create its own user and group, so you may have to perform a manual cleanup.I used to think that worries about what the Gnu build tools will make of /usr/local were verging on paranoid. Note that MacPorts creates its own user and user group. Warning: Don't run a sudo command-especially a rm -rf one-unless you know what it's doing, and enter each line individually if you're unsure. Sudo rm -rf /Library/StartupItems/DarwinPortsStartup Sudo rm -rf /Library/Receipts/MacPorts*.pkg Sudo rm -rf /Library/Receipts/DarwinPorts*.pkg Sudo rm -rf /Library/LaunchDaemons/org.macports.* If port is not found, try /opt/local/bin/port instead.Īlso, to remove remainders of MacPorts, you will need to delete the following files by this single command (copy and paste line-by-line to Terminal): sudo rm -rf /opt/local You need to first uninstall all ports: sudo port -fp uninstall -follow-dependents installed From the manual, uninstalling MacPorts works as follows.
0 kommentar(er)
