| > If I was to setup two completely seperate Xcode environments that I needed to run at the one time I think I'd probably investigate a chroot jail. And that's why you don't develop software for actual real human beings to use. > I'm not following. How does having shims for git prevent this? Because Xcode doesn't install any system components at all, the system itself provides the `xcode-select` utility that you use to select which Xcode version to use the tools from when invoking /usr/bin/git etc. If Xcode installed crap on the system, that would be impossible because each version of Xcode would have overwritten the other version's utilities. Not only that, but it would also break the ability to have 2 versions of Xcode, period, because the version that had its utilities overwritten would most likely break when the versions of the utilities change out from under it. > I thought this was rather obvious... Apple don't want people to symlink to other applications from /usr/bin just by exporting an environment variable. Well no, that's not the goal of SIP. SIP means nobody can muck with the system components. But the behavior you've described is the intended behavior of /usr/bin/git et al. The fact that these utilities are working as designed does not mean SIP is broken. > You were suggesting that Linux distributions installed shims in place of where the executables are normally No I didn't, I suggested that the fact that these shims suggest installing Command Line Tools is akin to how Linux distros often suggest installing packages via the package manager. I have no idea how you could possibly imagine I thought Linux added a shim for every single third-party utility in existence to /usr/bin. That's complete nonsense and I'm not sure how to interpret this as anything other than you insulting my intelligence. > You haven't really given a good reason why shims are required. I've given you multiple reasons, but you ignore most of them and suggest completely broken workarounds for the others. If you're going to pretend that I haven't explained numerous times why it works the way it does, I don't think there's any more point in talking to you. You're too focused on your broken solution to a complete non-problem for a system you don't understand in the slightest and you obviously don't want to actually bother to learn why they work the way they do. > You could actually run Xcode without the Xcode command line tools package Well yes, of course you can. The fact that you think that's a surprising statement means you don't even begin to understand how Xcode works or any of the stuff I've been explaining. Please stop parading your ignorance around. |
https://news.ycombinator.com/item?id=11652578
Feel free to comment there further if you want.
Peace :-)