![]() Then we just need a mapper file to map those brews with a different name than the port(s) it replaces. See Customized Setup of Toolchain section for some of the reasons. Then run through port_brews.txt and install each brew. MacPorts needs a full XCode installation, while homebrew only needs XCode command line tools. ![]() You could create a small script (ruby?) to run through list of brews and see if there is a port with the same name, then add the match to a port_brews.txt file. PS: Not sure how well this would work in practice!? Create script to run through unique_ports_installed.txt and call for each port_name (each line) I was running apache and php from macports, which was running smooth and I could work on my Symfony 3.3 development with that setup. Using Homebrew: brew install node Using MacPorts: port install nodejs. I recently switched from macports to homebrew. Library/StartupItems/DarwinPortsStartup \Ĥ. If your brew or cask is outdated, update and upgrade: brew update
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |