Homebrew El Capitan

  

I'm stuck to reinstall brew, ruby on El Capitan. Actually I didn't remember how exactly it occurs, but I lost my brew and I don't get reinstall it. This is the message I receive when I try to. To use git review, you have to be in a git clone directory that already contains a (possibly hidden).gitreview configuration file (see Gerrit/Advanced usage#Setting up a repository for git-remote) Mac OS X Method 1 (Homebrew) Works on OS X 10.11 El Capitan. The first method is termed as an upgrade install, also known as the default method. The second method is known as a clean install. Mac OS X El Capitan 10.11 DMG Install and Download. Upgrade install-Follow to below steps-Visit the Mac App Store. To upgrade from Lion or Mountain Lion, first upgrade to El Capitan, then upgrade to. Due to SIP restriction, the old HomeBrew(Migrated from Yosemite or older macOS) does not work well on El Capitan(and newer). $ brew update Error: /usr/local is not writable. You should change the.

OS X Homebrew packages¶ We generate Homebrew packages within our automated build system for the following OS X / Mac versions: OS X Mavericks (10.9) OS X Yosemite (10.10) OS X El Capitan (10.11) We only support 64-bit builds. If your system does not support these OS.

From the machine-learning-scientific-and-plotting dept. (71840) (26) by Luis

Here is a very quick way to install octave with aquaterm on Mac OS X 10.10 a.k.a. Yosemite as well as 10.11 a.k.a El Capitan. Note that these steps are not for the feign of heart and your millage might vary... Follow at your own risk.

updated 2016-11-21 22:32 GMT - tested with macOS Sierra (10.12) works well
updated 2015-10-07 21:58 GMT - tested with El Capitan (10.11) works well
updated 2015-06-21 09:17 GMT - adds homebrew/science tap
updated 2014-10-24 05:15 GMT - includes MacTex

Before you start you need to get your system setup. You will need:

  1. install Xcode from Apple's dev site
  2. install Xcode command line utilities from Xcode add-ons
  3. install hombrew
  4. install AquaTerm from sourceforge
  5. install Mac Latex (MacTex) from tug.org
  6. (optional) install Java

Yep, note that I'm assuming that you already have a working Homebrew installation, compilers, and AquaTerm ready... Then you may do:

  1. brew tap homebrew/science
  2. brew reinstall gnuplot --with-aquaterm
  3. gnuplot # make sure it says 'terminal set to aqua'
  4. brew install lua51 # yes, you also need this old version of Lua
  5. brew install octave

Installing Octave will take a while and it will install Lua 2.x as a dependency. If you see the make check | tee make-check.log taking an extremely long time. You might have to open a new terminal and navigate to cd /tmp/octave* and cat make-check.log to see where it went wrong. In my case it used to stop while loading lua dynlib files but installing the older lua51 fixed it.

When updating your operating system to a newer version of MacOS (macOS now), you may need to reinstall Octave if you see an error like:

Try: brew reinstall gcc arpack. If that does not fix it, then try: brew reinstall octave --without-arpack. And if this fails, you may use: brew reinstall octave --with-java.

Leave a comment if you need help, but this should do the trick ;) Now you can move on with your Machine Learning studies!

Here is a quick way to know everything works correctly:

  1. octave
  2. a = [2;3;4;5;6;3;4;32;3;2;1;4;5;6;7;]
  3. b = [12;23;44;55;66;12;44;9;5;27;111;23;66;89;88;]
  4. plot ([a, b])

Happy plotting!

I’ve already written a tutorial on how to set up a new Mac for Python-Django development with PostgreSQL as the database engine; however, that tutorial used the Python3 installer downloaded from the Python website. I recently got a new Mac, and I wanted to take this opportunity to learn how to set up my environment using other tools. Specifically, I wanted to download Python3 through Homebrew, a popular package manager for macOS.

Installing Python3 through Homebrew has its advantages, as many articles have stated. See the Further Reading section for a couple of those articles.

I thought about just updating my previous blog post, but a coworker suggested that I leave the old one, in case someone wants a reference for how to get a Mac up and running with the Python installer. So, here’s a whole new post for using homebrew to install several of the packages necessary for Python/Django development.

Before we get started, make sure you have disabled SIP, macOS El Capitan’s Rootless security feature. If you don’t know how to do this, see my other blog entry on how to do just that.

You’ll also want to install Xcode and all of the command line tools that Xcode can offer.

First off, we need to install HomeBrew. To do this, run the following:

To install the most recent version of Python3 via Homebrew, run the following in the terminal:

If you want to install a specific version of Python3 (i.e., Python3.4), Homebrew makes it a bit more difficult. Here’s an article on how to go about doing something like that.

There are a couple of things to note after your install of Python3. Mainly, if you’re used to the Python installer, Homebrew installs all of the Python files in different directories. It would be of benefit to become familiar with where your Python files have been installed.

Also, if ever you need to uninstall anything that you used Homebrew to install, you can run the following command:

Mac

brew uninstall package_name

If you’re comparing this tutorial with my other tutorial using the Python Installer, you’ll also note that I overwrite the symlinks for python, pythonw, pydoc, and python-config, as well as pip. This was strictly for the ability to say python in the terminal and invoke python3 instead. After writing that tutorial, I found that I never really needed that step, and therefore found it to be useless. So, we won’t be adding any symlinks here.

This section of the setup, though highly recommended, is optional. Virtual environments are a really great way to keep your machine clean and organized (concerning libraries/modules downloaded), and the most effective way to be able to run multiple python projects with different package version needs on one computer.

This section of the setup, though highly recommended, is optional. Virtual environments are a really great way to keep your machine clean and organized (concerning libraries/modules downloaded), and the most effective way to be able to run multiple python projects with different package version needs on one computer.

Note: If you’re interested in using virtual environments, you will need to have a project directory already planned for whatever project you’ll be working on.

Since brew-installing Python3 includes the pip3 package for virtualenv, we don’t need to worry about installing the package. Instead, we’ll hop right into creating our virtual environment, and move on from there.

Navigate from the terminal into the directory directly above the project directory where you’ll be working, and create your virtual environment. An important step here is to include the path of the Python interpreter that you would like to use.

Note: I say to create your virtual environment in the directory above your project directory only to avoid adding your virtualenv to your version tracking for the project (if you’re setting up your project with git, or another version tracking software).

At this point, you can activate your virtual environment and continue on.

Note: In your virtual environment, the “pip” command refers to “pip3”. Because of this, you’ll see throughout the rest of this (and the previous) tutorial that whenever I install a package via pip3, I only use “pip”. Be aware of this in case you’re using this tutorial without using virutal environments.

Now that python and pip are installed, it’s time to set up your database. I’m a big fan on Postgres as my database for django(-mako-plus) development, so here are the steps to getting your machine rolling with PostgreSQL.

As with Python3, I’ll be using Homebrew to install Postgres, only I’ll be installing Postgres9.4. To do this, run the following:

This should install and correctly symlink all necessary binaries for Postgres9.4. Next, start Postgres with the following:

IN A NEW TERMINAL TAB, create a new database, and attempt to enter the psql prompt:

If you’re able to get into the db, then you’re all set! Exit the psql prompt by entering the following into the terminal:

If you’re interested in ever using PgAdmin (a great GUI for interacting with Postgres), it’s recommended that you install the PSQL extension “AdminPack”. Do that with the following:

Finally, we’ll want Postgres to be running automatically each time we login or restart our computer. Do so with the following:

You can test that this worked by restarting your machine, then attempting to enter your “testing” database when your machine has restarted. If it didn’t work, then turn to Google.

Here is where the real beauty of installing with Homebrew comes to fruition. If you consult my other tutorial which uses the Python and Postgres installers, importing Psycopg2 can be a real pain. Usually you’ll need to go edit or create some symlinks to get it all to work. However, at the time of this writing, I was able pip-install Psycopg2 and successfully import it in a Python prompt without a hitch.

To do this, re-enter your virtual environment, and run the following:

Now from the python prompt:

If you don’t get any errors, then you’re all set!

If for whatever reason you do run into errors, then check my other tutorial in the Setting Up Psycopg2 section to troubleshoot.

Here are some other little tidbits of advice that might come in handy as you’re dealing with PostgreSQL on macOS.

Move Database (Data Directory) to a Different Location

In case you’re like me, and realize that you need more space on your machine, you might come across a time where you need to move an existing DB from one location/drive to another. Here’s how you go about doing that.

First, start by getting your drive mounted and formatted correctly. Then locate your data directory. To do this, log into the psql terminal as a superuser (this should be your normal macOS user) and show the data directory:

This should print out something like this:

That’s the location of the database files the Postgres binaries read and store data to.

Next, stop Postgres and move that directory to the desired location.

Homebrew El Capitan Software

Now create a symbolic link from the original location (inside of /usr/local/var/ to the new location, and restart Postgres

At this point, you’re all set to continue installing any other pip packages or modules that you need, and move forward with your project! Congratulations! You just installed everything with Homebrew!

Homebrew El Capitan Install

  • Blog Post on Updating PostgreSQL – Very useful
  • SO Article on Updating PostgreSQL via Homebrew – Pretty informative