It seems that "com.apple.pkg.CLTools_Base" was only used for one
release. New releases are using "com.apple.pkg.CLTools_Executables"
again.

Fixes Homebrew/homebrew#33063.

Closes Homebrew/homebrew#32394.

More Yosemite changes. Within two weeks or so, Xcode should be made
available on the App Store, at which point 10.9 will need to go from
“5.1.1” to “6.0” but whilst Yosemite is in Beta *everyone* should be
using the Xcode Beta builds according to Apple, so Yosemite should be
on 6.1 for the foreseeable, even when Apple releases Xcode 6.0 to 10.9
& below. 6.1 is still using the same Clang version number at this point.

Closes Homebrew/homebrew#32201.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Closes Homebrew/homebrew#31435.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Without this it’s impossible for brew-test-bot to be able to verify if
installing GCC has allowed it to fix a compiler selection failure.

The fact that this is implemented as a hash lookup is an implementation
detail, so don't let the KeyError bubble up.

Closes Homebrew/homebrew#30678.

This returns a list of symbols with the various CPU features supported
by the active hardware.

Closes Homebrew/homebrew#30296.

This reverts commit b0caede328b5181106451025df74a456276b76cf.

Fixes Homebrew/homebrew#30299.

Closes Homebrew/homebrew#30296.

Closes Homebrew/homebrew#29895.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>

Closes Homebrew/homebrew#29866.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>

See https://xquartz.macosforge.org/landing/



Closes Homebrew/homebrew#29826.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>

Closes Homebrew/homebrew#29823.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Fixes Homebrew/homebrew#27420.

Instead check if the path exists by using opt.

After recent cleanups the code in this branch should be unreachable, so
there is little point in keeping it around.

These methods are no longer required.

This reflects what Apple calls it in more recent versions of Xcode/OS X.

Since ae177adb2bd55ee5ad6367e7639c4cf0c774b63a, we can safely assume
that xcrun works, and a functioning xcrun will search dev_tools_path and
xctoolchain_path, so we can stop doing extra work here.

On CLT-only 10.7 and 10.8, xcrun will not work, but all the tools will
be in /usr/bin, which we check before invoking xcrun. Further, in this
case, dev_tools_path will be /usr/bin, and xctoolchain_path will not
exist, so the fallbacks here are unnecessary.