Git For El Capitan

  1. Git For El Capitan Download
  2. Git For El Capitan Free
  1. Git repository locked on El Capitan. Ask Question Asked 5 years, 2 months ago. Active 5 years, 2 months ago. Viewed 590 times 2. After installing El Capitan on my.
  2. While Apples comes out with their newest OS that is packed full of features, it can also pack some frustration for developers. I recently updated to El Capitan and thought everything was peachy. Unfortunately, when I ran a Git command recently, I ran into a road block.
  3. After upgrading to OSX El Capitan, I needed to turn off System Integrity Protection for directory modification commands to run properly. To turn off System Integrity Protection, follow below instructions. 1) Reboot your mac and press “cmd+r” when booting up. This will cause your mac to start in recovery mode. 2) Then go into utilities.
  4. El capitan theater beauty and the beast the sing a long los angeles. El capitan theater's theater los angeles. Reserve El Capitan Theatre parking through SpotHero. To find and purchase parking near the El Capitan Theatre in Los Angeles, select the date and time(s) for your desired reservation to view availability on the map or list.

I upgrated my os x from mavericks to EL Capitan and when want to use git in android studio, i got this error: xcrun: error: invalid active developer path (/Library. Bathroom design tool for mac freeenddwnload.

Inspired by a Gist from kevinelliott - thanks!

Install from App Store

  • Xcode - for command line tools required by Homebrew

Install from Third-Party Websites

Xcode Command Line Tools

Need to be installed for all the fne stuff in the latest section

Xcode > Preferences > Downloads > Command Line Tools


Run Xcode and accept the license! Homebrew can not install properly until this occurs.

Install Homebrew

If this is not a fresh install of Homebrew, go ahead and purge the complete installation first:

Now install Homebrew

Install common libraries via Homebrew

Install Cask application manager


Install applications via Homebrew Cask

The following software is still in testing and not part of my default setup:

Install Chrome extensions

Some extensions are not pulled from your Google account, so re-install theam manully now:

Firefox profiles

TODO make sure the profiles are registered

Git for el capitan free

After setting all the preferences, you need to reboot or at least restart Finder:

If you are curious, check this file for more possible settings.

Setup Github



Ruby & Gems

Prepare a sandboxed ruby environment

within we install some gems

Vagrant and plugins

Install custom .dotfiles at the end, cause we utilize some of the previously installed packages

Package Details: osx-el-capitan-theme-git 4.1.r2.gb245f91-1

Git For El Capitan Download

Package Actions

  • View PKGBUILD / View Changes
Git Clone URL: (read-only, click to copy)
Package Base: osx-el-capitan-theme-git
Description: Theme mimics OS X 10.12 macOS Sierra, formaly osx-el-capitan-theme, for GTK3 and some DEs (GNOME Shell, Xfce, Cinnamon)
Upstream URL:
Licenses: GPL3
Conflicts: gnome-shell-theme-osx-el-capitan
Submitter: orumin
Maintainer: Joel
Last Packager: Joel
Votes: 21
Popularity: 0.000000
First Submitted: 2016-05-14 04:16
Last Updated: 2019-07-05 05:37

Dependencies (5)

Git For El Capitan
  • gtk-engine-murrine(gtk-engine-murrine-git)
  • gtk3>=3.18 (gtk3-donnatella, gtk3-cosy, gtk3-adwaita-3-32-git, gtk3-mushrooms, gtk3-typeahead, gtk3-git, gtk3-ubuntu, gtk3-classic, gtk3-patched-filechooser-icon-view)
  • git(git-git)(make)
  • gnome-themes-standard (justbrowsing-theme, gnome-themes-extra)(optional) – Required for the GTK3 theme

Sources (1)

MoroS commented on 2019-03-11 11:29

The repo probably changed a lot in the passing year:

Git For El Capitan Free

Joel commented on 2017-11-11 00:30

heichblatt commented on 2017-11-07 09:35

Git for el capitan mac

This package, as mentioned before, makes every machine that has it installed update it every time the system is updated. The following patch fixes that. Please apply or orphan the package.
diff --git a/.SRCINFO b/.SRCINFO
index 63cff90.b3bc517 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
pkgbase = osx-el-capitan-theme-git
pkgdesc = Theme mimics OS X 10.12 macOS Sierra, formaly osx-el-capitan-theme, for GTK3 and some DEs (GNOME Shell, Xfce, Cinnamon)
- pkgver = 10.9.r8.g3dff454
+ pkgver = v0.9.r144.g6966a3a
pkgrel = 1
url =
arch = any
diff --git a/PKGBUILD b/PKGBUILD
index f2fd8dd.427e381 100644
@@ -5,7 +5,7 @@ _gitname=macOS-Sierra
pkgdesc='Theme mimics OS X 10.12 macOS Sierra, formaly osx-el-capitan-theme, for GTK3 and some DEs (GNOME Shell, Xfce, Cinnamon)'

steadybright commented on 2017-07-12 12:20

Yes, per dszryan's comment below, this package wants to be updated even though current version is already installed.

dszryan commented on 2017-05-10 08:51

the package is stuck in perpetual loop; requiring update

Joel commented on 2017-01-02 15:52

orumin commented on 2017-01-02 14:40

if you mentains VCS package(*-git), you should follow this guideline.
This guideline is recommend that pkgver is generated by git commit id or git tag with pkgver() function.
On now, newest git tag is 10.9. not v2.0.
Then, on -git package, don't use
and designate git repository on source variable as below:
pkgdesc='Theme mimics macOS 10.12 Sierra for GTK3 and some DEs (GNOME Shell, Xfce, Cinnamon)'
depends=('gtk3>=3.18' 'gtk-engine-murrine' 'gtk-engines')
optdepends=('gnome-themes-standard: Required for the GTK3 theme')
pkgver() {
cd '$_gitname'
git describe --long --tags sed 's/([^-]*-g)/r1/;s/-/./g'
package() {
mkdir -p '$pkgdir/usr/share/backgrounds'
cd '$srcdir/$_gitname'
mv 'Wallpaper.jpg' '$pkgdir/usr/share/backgrounds'
find . -type f -exec install -Dm644 '{}' '$pkgdir/usr/share/themes/macOS-Sierra/{}' ;

paulbarbee commented on 2017-01-02 02:47

I'm still getting the same error message as smnpl, both from installing via packer and from building via git.


Joel commented on 2016-12-30 16:24

smnpl commented on 2016-12-30 09:34

Hi, seems like the checksum is not valid anymore.
'ERROR: One or more files did not pass the validity check!'