![]() ![]() $ sudo port install gnupg curl wget ncftp tree pstree watch screen proctools mtr cowsayįor more info about installing and configuring PostgreSQL, see my post titled Installing PostgreSQL 9.0 on Mac OS X 10.6. $ sudo port install mercurial +bash_completion $ sudo port install git-core +bash_completion +doc +svn Just for my own sake and in case I need it in the future, I'm going to list a number of items that I had to reinstall: After closing the terminal and opening a new one, check the bash version using either of these methods:Īs long as the version displayed is the newer version from MacPorts, you should be ready to go.Use the chsh utility to change the shell to the new bash: chsh -s /opt/local/bin/bash.Add the path to the new bash ( /opt/local/bin/bash) to /etc/shells.So I decided to utilize the newer version of Bash installed by MacPorts and here's how: opt/local/share/git-core/contrib/completion/git-prompt.shīash Version 4.xAs I was reinstalling ports I noticed some logging that flew by in the terminal stating something about a requirement to use Bash 4 for the bash completion functionality to work properly. opt/local/share/git-core/contrib/completion/git-completion.bash As I mentioned in a previous post about this topic, the location of the location for the git-prompt.sh file had changed but this time I discovered that I had to source both the git-completion.bash file and the git-prompt.sh file to get things working. This provided a clean slate and everything worked without a problem, though I was annoyed that I had to take this drastic action and spend the time to get MacPorts working again.īash Completion For GitOne thing that I ran into was another change to the bash completion and prompt for git. After realizing that there were dependency resolution issues amongst different versions of dependencies for different ports, I decided to remove and reinstall MacPorts from scratch. 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.After trying to upgrade Mercurial to the latest version via MacPorts, I ran into some compilation issues with a couple dependencies that I could not resolve at all. 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 Double-check your desired ports are set as requested with port echo requested. ![]() Edit requested.txt to remove any ports that were not installed and repeat this step. Sudo rm -rf /Library/Receipts/MacPorts*.pkg Warning: if a port in requested.txt was not installed in the previous step, the iterative setrequested will terminate, leaving some ports still marked as not-requested. Sudo rm -rf /Library/Receipts/DarwinPorts*.pkg Sudo rm -rf /Library/LaunchDaemons/org.macports.* If you have a universal MacPorts installation on an Apple Silicon Mac, and you run it from a terminal emulator that is not a native arm64 binary, MacPorts will end up being run as x8664, and will build ports accordingly, which is often unexpected. 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 MacPorts defaults to building for the architecture that it is running as. You need to first uninstall all ports: sudo port -fp uninstall -follow-dependents installed From the manual, uninstalling MacPorts works as follows.
0 Comments
Leave a Reply. |