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:
A lightweight approach to removing Google web service dependency
In descending order of significance (i.e. most important objective first):
- ungoogled-chromium is Google Chromium, sans dependency on Google web services.
- 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.
- 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:
- Remove all remaining background requests to any web services while building and running the browser
- Remove all code specific to Google web services
- Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.
- 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).