> When I install VS I don't want other applications sharing dependencies with it to get upgraded or change.
Generally they won't change, you'll just get the security updates you would/should have installed anyway.
> No because the newer clang is not in the repo.
It sounds like you're adding a more bleeding edge repository that contains much more than just clang, is that correct? On debian based distro's I believe this can be done by pinning, but it's been quite a while since I've done that, from memory I do think it was a bit of a pain to setup correctly.
To understand the complaint I think you need to step back a bit. When someone wants to install a program on their box they are told to run: apt-get install XYZ (or through a GUI wrapper). You install it and everyone is happy.
A year later a new version comes out. The only way to get it is to upgrade your distro to a version that includes it in the repository.
Sure you have other alternatives like ppa's, .debs, and good old fashioned make install but now your off the happy path and into expert land.
Generally they won't change, you'll just get the security updates you would/should have installed anyway.
> No because the newer clang is not in the repo.
It sounds like you're adding a more bleeding edge repository that contains much more than just clang, is that correct? On debian based distro's I believe this can be done by pinning, but it's been quite a while since I've done that, from memory I do think it was a bit of a pain to setup correctly.