apt2ostree VS chromium

Compare apt2ostree vs chromium and see what are their differences.

apt2ostree

Build ostree images based on Debian/Ubuntu (by stb-tester)

chromium

The official GitHub mirror of the Chromium source (by chromium)
Our great sponsors
  • Sonar - Write Clean Python Code. Always.
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SaaSHub - Software Alternatives and Reviews
apt2ostree chromium
6 157
66 13,881
- 2.5%
4.4 0.0
about 2 months ago 2 days ago
Python
- BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

apt2ostree

Posts with mentions or reviews of apt2ostree. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-11.
  • Why Use Make
    10 projects | news.ycombinator.com | 11 Jan 2023
    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

  • An ode to Flatpak (and Fedora Silverblue)
    6 projects | reddit.com/r/linux | 21 Aug 2022
    However, you can get pretty close yourself with a tool like this https://github.com/stb-tester/apt2ostree
  • Docker containers usually still reachable even if bound to 127.0.0.1
    5 projects | news.ycombinator.com | 22 Jun 2022
    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

  • Reproducible builds for Debian: a big step forward
    4 projects | news.ycombinator.com | 12 Oct 2021
    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/

chromium

Posts with mentions or reviews of chromium. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-19.

What are some alternatives?

When comparing apt2ostree and chromium you can also consider the following projects:

ungoogled-chromium - Google Chromium, sans integration with Google

WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.

bromite - Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser!

brave-browser - Next generation Brave browser for Android, Linux, macOS, Windows.

termux-packages - A build system and primary set of packages for Termux.

gecko-dev - Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

sciter-js-sdk - Sciter.JS - Sciter but with QuickJS on board instead of my TIScript

iceraven-browser - Iceraven Browser

brave-core - Core engine for the Brave browser for Android, Linux, macOS, Windows. For issues https://github.com/brave/brave-browser/issues

fingerprintjs - Browser fingerprinting library. Compared to Fingerprint Pro has limited accuracy (40 - 60%), but is fully open source.

aniyomi - Unofficial fork of Tachiyomi for anime

Fenix - Firefox for Android