<i>&gt; • Xcode is a self-contained app bundle, it does not install components across the system, which would be required for your scheme. This is intentional for several reasons.</i><p>A self contained app bundle that does not install components across the system and requires access to common executables that redirect access to utilities shared amongst the app bundles.<p>Doesn&#x27;t that tend to break the self-contained nature of the packages?<p>If I was to setup two completely seperate Xcode environments that I needed to run at the one time I think I&#x27;d probably investigate a chroot jail.<p><i>&gt; • Having 2 copies of Xcode installed at once is explicitly supported. This requires that Xcode not be installing components across the system or it they would interfere with each other.</i><p>I&#x27;m not following. How does having shims for git prevent this?<p><i>• Your description of xcode-select is overly-convoluted. In practice it&#x27;s really very simple. xcode-select sets the default Xcode installation used for xcrun and the shims. You can override this selection on a per-invocation basis by setting the DEVELOPER_DIR env variable instead. If you don&#x27;t have the env variable set, xcode-select is roughly equivalent to replacing all of the shims with symlinks that point into the selected directory. And you haven&#x27;t explained why any of this is supposed to increase the &quot;attack surface&quot;.</i><p>I thought this was rather obvious... Apple don&#x27;t want people to symlink to other applications from &#x2F;usr&#x2F;bin just by exporting an environment variable.<p><pre><code>  630188s-iMac:~ 5K$ mkdir -p ~&#x2F;xcsl&#x2F;usr&#x2F;bin
  630188s-iMac:~ 5K$ echo &#x27;#!&#x2F;bin&#x2F;sh&#x27; &gt; ~&#x2F;xcsl&#x2F;usr&#x2F;bin&#x2F;xcrun
  630188s-iMac:~ 5K$ echo &#x27;echo &quot;Hello world!&quot;&#x27; &gt;&gt; ~&#x2F;xcsl&#x2F;usr&#x2F;bin&#x2F;xcrun
  630188s-iMac:~ 5K$ chmod a+x ~&#x2F;xcls&#x2F;usr&#x2F;bin&#x2F;xcrun
  630188s-iMac:~ 5K$ export DEVELOPER_DIR=~&#x2F;xcsl&#x2F;
  630188s-iMac:~ 5K$ git
  Hello world!
</code></pre>
Notice something? No sudo needed.<p><i>&gt; • You keep claiming that this defeats the purpose of SIP, which makes no sense at all. I can&#x27;t even figure your logic for claiming it defeats SIP, which makes me wonder if maybe you&#x27;re just trying to spread FUD.</i><p>See above.<p><i>&gt;• I absolutely do know how Linux distros suggest packages, please don&#x27;t try to tell me that I don&#x27;t.</i><p>You wrote:<p><i>&quot;All that you&#x27;ll have are a set of shims that offer to install the developer tools if you try and run them (which I hope you can see is a pretty sensible suggestion, and is akin to how linux distros often suggest packages you can install when you try and execute commands that don&#x27;t exist).&quot;</i><p>You were suggesting that Linux distributions installed shims in place of where the executables are normally (&quot;All that you&#x27;ll have are a set of shims [which are] akin to how linux distros often suggest packages you can install when you try and execute commands that don&#x27;t exist&quot;). All I was saying is that Linux distros don&#x27;t install shims.<p>If you meant something other than that I&#x27;m not sure what your point about Linux was given they have a very different mechanism for suggesting packages. Probably the biggest difference, even beyond the shim point, is that they don&#x27;t actually prompt you to install the package...<p><i>&gt; • Using bash v4 is not more sensible than installing a shim, because, as I&#x27;ve explained at great length, is required for reasons other than just suggesting the installation of Command Line Tools. You keep ignoring all of the reasons why this is required for current functionality and are focusing on the single aspect, of suggesting the installation of Command Line Tools, that could conceivably be done a different way.</i><p>Indeed, I am :-) You haven&#x27;t really given a good reason why shims are required. I&#x27;ve shown how they can be abused above. I&#x27;m happy to agree to disagree though!<p><i>&gt; • Besides, saying &quot;use bash v4&quot; is not a solution anyway, because many people do in fact switch their default shell, at which point they&#x27;d lose the instructions on how to install the command-line tools.</i><p>You mean the people who know how to install and use a different shell to bash? The same people who have worked out how to install packages from the command line, such as <i>xcode-select --install</i>? Or perhaps you mean those folks who use an alternative package installer like homebrew who know that you just have to run <i>brew install git</i> because they ran <i>brew install zsh</i> to install their alternative shell?<p>I don&#x27;t think it&#x27;s going to fuss them too much personally.<p><i>&gt; I&#x27;d really rather you don&#x27;t give me another long-winded reply that boils down to you saying &quot;I don&#x27;t understand the point of SIP or how it works, or how Xcode&#x27;s self-contained app installation works&quot;.</i><p>Given I didn&#x27;t do that, I can&#x27;t exactly give you &quot;another&quot;. I do understand the point of SIP, and I think it&#x27;s kind of interesting that you think that a shim is required for anything other than prompting the user how to install things like git. You could actually run Xcode without the Xcode command line tools package, and you could quite easily install git yourself and have everything else work.<p>Anyway, I&#x27;m detecting that you are beginning to get a bit personal so I think I won&#x27;t say anything further other than I respectfully hope we can agree to disagree!