Why did Apple Decide not to install Command Line Tools which now have to be installed through xcode?

closed as primarily opinion-based by nohillside Aug 27 '13 at 3:38

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Most of the binaries are already included in /Applications/Xcode.app/Contents/Developer/{Tools,usr/bin}, and you can use commands like xcodebuild -find SetFile to find paths to them. Other App Store applications wouldn't be allowed to modify /usr/bin/ either. – Lri Aug 27 '13 at 3:50
  • If there is a practical question you're looking to solve, let's edit that in so we can look at re opening this. – bmike Aug 27 '13 at 10:01

To answer your question, not many (relative term here) OS X users will install or have any need for command line tools because it is part of a larger group of tools to download. A large majority of regular, everyday OS X users won't be using these programs. However, you do not have to install Xcode to install command line tools anymore.

Sign in to Apple's Developer Downloads Page and then search for Command Line Tools.

Download and install the latest as a .dmg.

enter image description here

Related Question: How to download the Command Line Tools for Xcode without the Downloads for Developers webpage?

Alternative Way

As referenced from a Stack OverFlow post, here is an unofficial link to the March 2012 Command Line Tools for Xcode.

Not the answer you're looking for? Browse other questions tagged .