Google Chrome Apt Sources
I will die on this hill: There's nothing like reading the source code!!! If you're like me and you're getting sick of Google Chrome managing your apt-sources for you, I have news for you: it's possible to bypass the scripts automation from managing the files for you. Simple answer: mv /etc/apt/sources.list.d/google-chrome.list /etc/apt/sources.list.d/g-chrome.list Just move the old legacy sources.list to another name not expected by the script. If it's absent AND /etc/apt/sources.list.d/google-chrome.sources is absent, it won't try to manage the repo for you. Why am I doing this? On my system, I had Google Chrome installed and configured to use my Architecture (amd64), but can still run Steam (i386) alongside without issues. Google Chrome started changing the way they managed /etc/apt/sources.list.d/ and started using the .sources format which is multi-line instead of the 1-liner format. In doing so, they completely neglected to include the architectu...