Found some patches for ungoogled-chromium-windows https://github.com/Nifury/ungoogled-chromium-windows/tree/master/patches
Some of them might be useful for this pkg?
BTW, I've checked some, but none is critical.
Git Clone URL: | https://aur.archlinux.org/ungoogled-chromium.git (read-only, click to copy) |
---|---|
Package Base: | ungoogled-chromium |
Description: | A lightweight approach to removing Google web service dependency |
Upstream URL: | https://github.com/ungoogled-software/ungoogled-chromium |
Keywords: | blink browser privacy web |
Licenses: | BSD-3-Clause |
Conflicts: | chromedriver, chromium |
Provides: | chromedriver, chromium |
Submitter: | ilikenwf |
Maintainer: | JstKddng (networkException) |
Last Packager: | networkException |
Votes: | 354 |
Popularity: | 5.23 |
First Submitted: | 2016-12-19 08:08 (UTC) |
Last Updated: | 2024-11-20 21:14 (UTC) |
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 66 Next › Last »
Found some patches for ungoogled-chromium-windows https://github.com/Nifury/ungoogled-chromium-windows/tree/master/patches
Some of them might be useful for this pkg?
BTW, I've checked some, but none is critical.
I think so...Do I need to delete pamac's/pikaur's temp/cache folders or soemthing?
@IEPforAUR
are you doing a clean build? The OBS built fine btw.
error: unknown type name 'FT_ClipBox'
@RonnyD
I think that could be possible on the -git package, I'm not sure if it'd be any faster though.
I agree with @RonnyD. I at least tried forcing ccache but it does not seem to have any effect, it's still a 4 hour wait to build.
Would there be any way to keep cached compiled files across updates? I recon not all source files need recompilation every time. This would probably drastically speed up compilation times, especially on lower end hardware.
Maybe this could be done setting a specific temporary directory when using an AUR helper (trizen, paru, yay, etc.)?
sorry for not noticing the need for an update, looks like my mail server is not working properly. I'll update once OBS build is succesful.
@followait: The Home URL is not patched into this package. It rather looks like chromium
recognizes your /etc/os-release
file.
You can also verify this by checking the About
page with the chromium
version info: At the end of the version info, Manjaro Linux
is displayed if you are running Manjaro
.
@followait: Ask in the Manjaro User Repository, this is the Arch User Repository.
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