@bsdice
// You already know about my repository, there really isn't a shorter way about it.
// Next, the OBS is needed as a build box, nothing else, not everyone has a 16 core 32 t rig in order to build this. And I don't think it could be adopted to the main repositories as Arch tries to keep the packages as pristine as possible, as in, without any non-REQUIRED patches.
// Finally, you could take that recommendation to the aur-general mailing list, they will probably just tell you to just open an orphan request if the current owner doesn't update promptly.
@Rowisi
I just don't see any way possible to have an ungoogled-chromium-bin package which would not require repackaging and don't be a pain when some library gets updated which breaks some binary because it was linked to the older version. I've gone through that, it's not entertaining.
Regarding the OBS, Eloston could ditch the ungoogled-chromium-binaries organization and just switch to an organization in the OBS.
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