About 3 years ago, fredx181 came out with the 'portable' Firefox browser everything self-contained in a single location, and run from a single launcher. This was, however, very time-consuming, despite doing what I wanted. Initially, I did what davids45 recommended set up an external filesystem on a remote partition, and sym-link everything I wanted or needed into each Puppy at the relevant locations. It then occurred to me what a waste of disk space this was duplicating the same stuff I don't know HOW many times, over & over again.space that could be better used for the user's own personal data/work. In the early days with Puppy, I used to install a fresh copy of every app to each new Puppy, along with all its config/setting stuff. They run perfectly happily from a flash drive, too. These portable browsers can be run from Puppy's /mnt/home (sorry, I don't know FatDog's equivalent to /mnt/home), or from anywhere outside the OS itself. This can be located externally to your various OSs - in a location accessible to all - then be 'shared' between multiple Puppies/derivatives. The whole idea is that you have ONE copy of your config settings, bookmarks, extensions, etc., because the browser profile is located inside the portable's directory. to exclude bookmarks, apps, history, passwords, etc.? I am not sure but it looks like settings are stored in ~/.config/google-chrome/Default/Preferences in jason format.ĭo you know if it is possible to manually export only the Chrome settings to another FatDog Chrome installation without having to sync and backup all data ie. Yes, there is a google-chrome folder in /home/username/.config. They simply wouldn't bother.which is why Windows Update, for instance, does it totally automatically in the background. Most folks, if left to their own devices, would happily roll along with the same version of most items for years at a time. Not everybody religiously updates to the very newest versions of everything, the instant they become available.! Far from it. He's even taken a leaf out of Google's own book although Chromium itself always expects the very newest of everything, Marmaduke's builds are compiled against a somewhat older kernel/glibc/deps combination, which makes it more widely usable by a greater number of people. Unlike some packagers, Marmaduke has got his AppImage spot-on, and it works everywhere. The AppImage is what I build the Ungoogled_Chromium-portable package around, which just keeps all its config stuff self-contained within its own directory. Marmaduke offers this as a standard tarball, and also as an AppImage. It's perfectly possible to add extensions, etc, from the Chrome Web Store, though it does entail a somewhat convoluted process you're having to perform the same steps, manually, which Chrome itself performs automatically. This build includes all the necessary multimedia codecs'n'stuff, as well as current Widevine DRM, and support for VAAPI video hardware decoding is built-in. This is where I found the UnGoogled Chromium builds by "Marmaduke". There IS a website where you can find pre-built packages, though these are all 3rd-party ones usually built by individuals, who then make their packages publicly available:. Most distros take the source code, compile their own builds of the browser, and offer it to their users through the package managers. Google wanted to make the code open-source and publicly available to all.unlike the incumbent at the time, Internet Exploder, which was very much closed-source & proprietary. It was set up at the same time as the Chrome alpha/beta test releases way back in the late summer of 2008, when the whole thing was getting under way. The Chromium Project is effectively Google's R&D department for Chrome itself. There is no such thing as a downloads page for Chromium, for "official", pre-built Chromium packages. Unfortunately, Jim's right about this one. Check Ungoogled-chromium, SR Iron Browser, and many others. better security, no Google telemetry, and stuff like that). Otherwise, if you are only interested in the browser, there are many Chromium-derivative browers that are more interesting because they offer you features you can't find in Chrome or Chromium (e.g. I'm talking about the app framework, not the one that orbits inside the atom. Really the interest for Chromium is for anyone who wants to download the source code, and tweak it, and build something out of it. In other words, Chromium is Chrome, without the shiny parts, but with the extra bugs.Ĭhromium in itself is rather not interesting. Once they hit a particular milestone, or consider it to be "stable", then they add the juicy bits and release it as "Chrome". It's a test harness for Chrome as Google develops it. I am fine with Chrome, I was just wondering.Ĭhromium is Chrome with its "proprietary component" removed. What was the reason to include Chrome over Chromium?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |