Google only packages Chrome for Ubuntu (deb) officially. If you are not using Ubuntu, you are probably not using Chrome directly from Google. However, if you use flatpaks you might as well trust this one package from flathub since the trust model is the same.
Maybe. I'm more comfortable signing into my accounts using Chrome packaged by Google than by a third party. I should probably familiarise myself with the linked repo to show I'm worrying about nothing.
Google's solution for Chrome on Debian and Ubuntu is to distribute a .deb package that installs not only Chrome, but also installs a reference to their own package repository. When the user updates packages on their system, it updates Chrome from Google's repository. Chrome does not update itself, nor can it, since the package installs it to /usr/bin, which would require a su/sudo prompt to get access to.
Going to googles official webpage will tell you how to get chrome for Debian/Ubuntu/Opensuse/Fedora. This is about as good as it can be because chrome is closed source.
The official Google Chrome .deb for Debian/Ubuntu downloaded from google.com/chrome sets up a software source as well, so you can't say that's not how .deb files work.
kerrick@psyduck:~$ ls /etc/apt/sources.list.d/
google-chrome.list
kerrick@psyduck:~$ cat /etc/apt/sources.list.d/google-chrome.list
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://dl.google.com/linux/chrome/deb/ stable main
Sure it’s using system ones and not the vendored ones? I mean chrome as packaged by Google, not, say, Fedora’s Chromium (which is bent and coerced to use system libraries as much as possible).
By the way if you are installing google chrome with linux packages, it says the same. It frightened me at first I was like, whose organization is managing my "google-chrome" install? Then realized my organization was just the root account on my linux vs installing chrome a different way (flatpak, manual install in homedir).
And last I looked, that's how Chrome/Linux works too, at least on Ubuntu. When you download and install the deb, it'll set up apt sources so you get updates through the system.
Apparently Google agrees: when you install Chrome on Ubuntu it uses the OS's update manager to keep itself updated (by adding its own APT repository). Nifty.
reply