apt2ostree VS ungoogled-chromium

Hm yes now I remember that point about how the data is anonymous Python objects that you can pass around to functions.

Are there any open source examples? I looked around the github account, but I mostly remember this tool

https://github.com/stb-tester/apt2ostree

I'd be interested in seeing the Python config and Ninja output, to see how it works. Right now it looks to me like the dependencies are more implicit than explicit, e.g. with your copen example

---

The system I ended up with is more like Bazel, but it's not building containers, so it's a slightly different problem. But I'm interested in building containers incrementally without 'docker build'.

I like the apt lockfile idea definitely ... However I also have a bunch of other blobs and tarballs, that I might not want to check into git. I guess you just put those in OSTree?

Our config looks like this

https://github.com/oilshell/oil/blob/master/core/NINJA_subgr...

And all the code is in build/ninja* of the same repo

However, you can get pretty close yourself with a tool like this https://github.com/stb-tester/apt2ostree

With apt2ostree[1] we use lockfiles to allow us to version control the exact versions that were used to build a container. This makes updating the versions explicit and controlled, and building the containers functionally reproducible - albeit not byte-for-byte reproducible.

[1]: https://github.com/stb-tester/apt2ostree#lockfiles

If you have time to test things, you can try to use ostree to manage a Debian installation. This is what Silverblue uses. Their is already a tool to create APT-based ostree images.

On the subject of reproducible debian-based environments I wrote apt2ostree[1]. It applies the cargo/npm lockfile idea to debian rootfs images. From a list of packages we perform dependency resolution and generate a "lockfile" that contains the complete list of all packages, their versions and their SHAs. You can commit this lockfile to git.

You can then install Debian or Ubuntu into a chroot just based on this lockfile and end up with a functionally reproducible result. It won't be completely byte identical as your SSH keys, machine-id, etc. will be different between installations, but you'll always end up with the same packages and package versions installed for a given lockfile.

This has saved us on a few occasions where an apt upgrade had broken the workflow of some of our customers. We could see exactly which package versions changed in git history and roll-back the problematic package before working on fixing it properly. This is vastly better than the traditional `RUN apt-get install -y blah blah` you see in `Dockerfile`s.

IMO it's also more convenient than debootstrap as you don't need to worry about gpg keys, etc. when building the image. Dependency resolution and gpg key stuff is done at lockfile generation time, so the installation process can be much simpler. In theory it could be made such that only dpkg is required to do the install, rather than the whole of apt, but that's by-the-by.

apt2ostree itself is probably not interesting to most people as it depends on ostree and ninja but I think the lockfile concept as applied to debian repos could be of much broader interest.

[1]: https://github.com/stb-tester/apt2ostree#lockfiles

[2]: https://ostreedev.github.io/ostree/

Cromite[0] is the best on Android, it's a privacy-oriented open source patchset on top of Chromium.

Cromite has a desktop build, but it's a bit more experimental than the mobile build, so you can use Ungoogled Chromium[1] instead. Ungoogled is also a privacy-oriented open source patchset on top of Chromium. Check the beta flags to enable some more interesting features like getClientRect anti-fingerprinting measures (unfortunately breaks some React-based sites that go into infinite re-render loop).

Both of these browsers selectively include patches from Brave, but they are community-oriented builds so imo more trustworthy than Brave, which continues to package various shady anti-features and always will because it's backed by a for-profit company.

LibreWolf[2] is the nicest Firefox-based one for desktop, I think. It's pretty hardcore, though, I most only use it to visit mainstream social media sites.

I tried a bunch of the Firefox-based ones on mobile and none of them clicked for me. Cromite is just too slick on Android. Put the address bar at the bottom and off you go. Only downside is no online syncing of tabs and bookmarks, but meh. You can save all open tabs to bookmark bar in one hit then export your bookmarks, send the file through whatever E2EE channel you want to your other device and import then reopen them again.

[0] https://github.com/uazo/cromite

[1] https://github.com/ungoogled-software/ungoogled-chromium

[2] https://librewolf.net/

For those that like Chromium but want to remove any integration with Google, there's Ungoogled Chromium

https://github.com/ungoogled-software/ungoogled-chromium

If you're entirely partial to Chromium browsers, use Ungoogled Chrome https://github.com/ungoogled-software/ungoogled-chromium

what about https://github.com/ungoogled-software/ungoogled-chromium

Firefox or Ungoogled Chromium (needs to update uBlock manually) in Incognito window with unchanged vanilla uBlock Origin with lists updated and no other plugins and without YouTube account. Works perfectly. Also FreeTube.

Ungoogled Chromium is a Chromium-based browser with Google services stripped out.

- Project and source: https://github.com/ungoogled-software/ungoogled-chromium

- Binaries: https://ungoogled-software.github.io/ungoogled-chromium-bina...

Using these sort of downstream patch set browsers is rarely a good idea. If it has multiple full-time developers from a respected org dedicated to it, then it can be justifiable (Tor Browser, Brave), but take a look at the gaps in time for these two pages:

https://github.com/ungoogled-software/ungoogled-chromium/rel...

https://metadata.ftp-master.debian.org/changelogs//main/c/ch...

There's often days you're going without security patches. If you want a browser without Google tracking, Firefox is a much better choice.

While these screenshots use Google Chrome, they will also work on all 'Chromium' based web browsers, like Brave, Vivaldi, ungoogled-chromium, etc. Window's Edge is also compatible, though some the button locations are changed.

I would highly recommend the Ungoogled Chromium fork instead: https://github.com/ungoogled-software/ungoogled-chromium

Entirely volunteer maintained, there is no for-profit entity behind it looking to do crypto referrals or ad swapping or anything like that.