Add Ungoogled Chromium to Manjaro's repos (from their official obs arch repo)

Last time this package was requested the request was negated because there was no one willing to build every time a chromium fork (it is a very very long process). Fortunately now the Ungoogled Chromium team has an official repository on the Opensuse Build Service that automatically produce the binary for arch from their arch Github repo, so now porting this is just matter to push the update update from their repo to Manjaro’s ones when the dependencies of the browser are satisfied by the packages in the repo.

For anyone who doesn’t know what Ungoogled Chromium is, here is an extract from their main Github repo:

ungoogled-chromium

A lightweight approach to removing Google web service dependency

Objectives

In descending order of significance (i.e. most important objective first):

  1. ungoogled-chromium is Google Chromium, sans dependency on Google web services.
  2. ungoogled-chromium retains the default Chromium experience as closely as possible. Unlike other Chromium forks that have their own visions of a web browser, ungoogled-chromium is essentially a drop-in replacement for Chromium.
  3. ungoogled-chromium features tweaks to enhance privacy, control, and transparency. However, almost all of these features must be manually activated or enabled. For more details, see Feature Overview.

In scenarios where the objectives conflict, the objective of higher significance should take precedence.

Motivation and Philosophy

Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.

ungoogled-chromium addresses these issues in the following ways:

  1. Remove all remaining background requests to any web services while building and running the browser
  2. Remove all code specific to Google web services
  3. Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.
  4. Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).
2 Likes

And the last build, from 24th of April, failed and there is no package created…

3 Likes

Ungoogled chromium would be a good alternative to add to the repos. Let’s see what can be done.

3 Likes

I’ve got this installed through Flathub I think and it updates through Pamac. Handy to have for every now and then when a website doesn’t play nicely with Firefox.

The pacakge still need to be build natively on Manjaro, on all branches

Can you prove that is official? From Eloston github page:

NOTE: These binaries are provided by anyone who are willing to build and submit them. Because these binaries are not necessarily reproducible, authenticity cannot be guaranteed;

Eloston don’t seem to provide any official package

That Arch github repo is stuck at 25 December 2020 at v87.0.4280.88-3

About the first concern I don’t know what to say: right now I use some unofficial binaries (still made by one of the contributor of the project) build for arch and I update them manually whenever, after a manjaro update, the previous version didn’t work anymore because some mismatch in the dynamic libraries (or if a new chromium version is released I, after testing, it still seams to work on my manjaro machine, otherwise i downgrade to the previous version).

Their github repo for arch gets new commits quite often (last one is 3 days old at the moment): what are you seeing was some sort of experiment on some ideas on how to provide prebuild binaries I think (the guy that releases them is the contributor from which I get my binaries). If you want to see which is the last released version you can simply go on aur and see the version there (the PKGBUILD came from their repo).

As said in the readme of their main repo the binaries are not reproducible, so you can’t trust anyone who publish some binaries, but, in order to solve this problem, they decided to use the OpenSuse Build Service that directly takes the sources from their repo (the PKGBUILD and the other patches) and build the package (so you are sure that is has not been tampered, at least if you trust opensuse).

Right know they have some problem building chromium (with or without any patches) because of the new default cflags used by arch recently, but I think that in a few days everything will be sorted and the package will be available on obs.

Packages need to be build natively on Manjaro, on all branches, by some Manjaro developer, you can’t add to the repos packages builded on Arch from ‘untrusued’ people

The binaries are build on obs (instead of manually by someone on their own machine) for that exact reason.

Still irrilevant for the addition to Manjaro repo

Still the version is v87.0.4280.88-3 at 25 December 2020

I installed ungoogled-chromium-bin through the chaotic-aur repo but it would be nice if it was in the official Manjaro repositories.

1 Like

Has I said, you have to look into the PKGBUILD on the repo (or on aur, it cames from that repo anyway): the version is “90.0.4430.93” (the version bump has been done 11 days ago).

About this I don’t understand your point (or if you are just trying to start a flame): the software is open, you can build yourself or save hours of time and using obs that grantees you the binaries that comes from the sources you feeded it (you can see exactly the sources of the package you are downloading from there). Moreover it is not even that Manjaro (or Arch) uses only open source code for the packages in their repos (examples are steam, or the firmwares in the “linux-firmware” package)

Yeah, I missed it, I looked at the releases and looked a bit at the commits but didn’t see the package update

The package need to be build natively on Manjaro, for all branches

I am aware of the difference between OSS and proprietary thanks