title: Homebrew Permissions mess
body: <p>I installed Homebrew from my admin account. If I run <code>brew doctor</code> from that account I get no errors, but if I run <code>brew doctor</code> from my non-admin user account, I get warnings about several directories (<code>usr/local</code> and its subdirectories) not being writable, and suggestions that I <code>chown</code> them.</p>
  
  <p>More recently, I installed RVM from my non-admin account (to ensure it was usable to that user and installed in their home directory). I then ran <code>rvm install 1.9.3</code> (again, as non-admin) and got an error warning me that <code>usr/local/bin</code> isn't writable and is required for Homebrew. Running <code>rvm requirements</code> yields the same warning.</p>
  
  <p>Am I supposed to install RVM as non-admin, switch to admin when I install ruby version <em>with</em> RVM, and then be able to use RVM (for everything other than installing) from the non-admin account? Or is something else wrong here?</p>
  
  <p>The RVM output when I attempted to install 1.9.3 follows:</p>
  
  <pre><code>$ rvm install 1.9.3
  Searching for binary rubies, this might take some time.
  No binary rubies available for: osx/10.8/x86_64/ruby-1.9.3-p448.
  Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
  Checking requirements for osx.
  ERROR: '/usr/local/bin' is not writable - it is required for Homebrew, try 'brew doctor' to fix it!
  Requirements installation failed with status: 1.
  </code></pre>
  
  <p>It's been suggested to me that I shouldn't have installed Homebrew while logged in as an admin, so I should uninstall (as admin), then reinstall as a regular user. I tried this, but when I run the install script as a regular user, the first thing it tells me is:</p>
  
  <pre><code>$ ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)"
  This script requires the user myuser to be an Administrator. If this
  sucks for you then you can install Homebrew in your home directory or however
  you please; please refer to our homepage. If you still want to use this script
  set your user to be an Administrator in System Preferences or `su' to a
  non-root user with Administrator privileges.
  </code></pre>
  
  <p>I imagine this is why I installed it as an admin in the first place. Any help clarifying this?</p>