BostonPeng wrote:I love using Chromium and would like to find an easy way to keep the newest version on my drive without having to use the Google tracking and branding. I see Debian has a newer version in Sid, but if I add that repo (once I find the code to do it, of course), will having that repo active cause problems for other apps in LMDE? I'm already risking borking my system by using KDE (yes, I'm too impatient to wait for the official LMDE KDE release :p) and I'd prefer to keep conflicts and confusion to a minimum this time around.
From what I've read, Chrome tracking is fearmongering
. I do run the disconnect
, and keep my opt outs
extensions, since I can't control what Google's servers do. (I should note, one of these seems to play heck with redirects when I hit a URL like code.google.com that expects an account login.)
There's an (unofficial?) link to the latest build at getchromium.org
. My feeling running chromium snapshots for the past year, though, is that you're gambling with showstopper bugs in the daily builds, and better off with some degree of quality control (either Google's release manager, or the DM
). The Chrome unstable/dev channel tracks these builds pretty closely, without most of the headaches.
I can usually get away with repo-swapping in /etc/apt/sources.list
, grabbing the update, and swapping back, but there's always a chance it will backfire.
Note apt-listbugs currently shows:
grave bugs of chromium (13.0.782.107~r94237-1 -> 15.0.874.106~r107270-1) <unfixed> #648015
- chromium: fails to render any web page