TLDR: My gripe here is the continuing departure from Arch in-universe methods of delivering this package. Everyone contributing to this package is creating value, but that comes with another single point of failure. Shouldn't this be improved?
// The critical chain is getting really long. Chromium -> Eloston Github -> JstKddng Github -> Rowisi Github -> Opensuse Build Service -> User download and usage. Looks very scary. Any way to shorten this?
// Why is OBS even needed? What would it take to have the package in the community repo? No trusted user liking this package enough? One would think Google the company has damaged Chromium enough already to make a desktop Linux user switch to this package.
// Since the internet browser is the most security-critical component in any modern Linux desktop, I cannot with good conscience roll this out to friends and family Linux desktops. I would really want to. Having compiled this package over 20 times myself, I get that this is one complicated beast. Also on a long enough time scale, people go away. They switch distributions, marry, die, take up shrimp farming instead whatever. What we lack in AUR here is what Github has made big:
-
projects can be run by a group not single persons, to increase the bus factor above 1
-
pull requests for contributions, to lighten maintainer workload
-
continuuous integration, to automate new builds for distribution
// Does Arch need more money for infrastructure to make this happen?
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks