mirror of
https://abf.rosa.ru/djam/chromium-browser-stable.git
synced 2025-02-23 22:52:49 +00:00
6aceefa0d9
- first build of v89 - replaced custom BUILD.gn with a patch of source code; we may just miss that custom BUILD.gn has stopped working, but we will explicitly detect the moment when applying patch fails (custom BUILD.gn may be restored later if it makes sense to reduce maintenance burden) - dropped build-with-pipewire-0.3.patch, upstream now supports both pipewire 0.2 and 0.3 - took updated chromium-40-sorenson-spark.patch and chromium-55-extra-media.patch from Mageia (I want to remove these patches actually) - dropped some patches with not needed compiler-related changes - spec clean up: + removed not used for a long time support of building with GCC (Chromium upstream has tight integration with clang, I don't think that we will ever need buildability with GCC, for now it may be broken and just makes the spec more complex) + removed switches of libpng and vaapi without changing their values to redcue complexity of the spec - removed not used VA-API patch, replaced with VA-API enhacements from ppa:saiarcot895/chromium-beta, including support of VA-API VDPAU backend on Nvidia proprietary drivers
14 lines
669 B
Diff
14 lines
669 B
Diff
--- chromium-89.0.4389.82/chrome/browser/first_run/first_run_internal_linux.cc.orig 2021-03-07 14:49:07.372334047 +0300
|
|
+++ chromium-89.0.4389.82/chrome/browser/first_run/first_run_internal_linux.cc 2021-03-07 14:49:57.910937907 +0300
|
|
@@ -19,9 +19,9 @@
|
|
|
|
base::FilePath InitialPrefsPath() {
|
|
// The standard location of the initial prefs is next to the chrome binary.
|
|
+ // ...but we patch it to use /etc/chromium
|
|
base::FilePath initial_prefs;
|
|
- if (!base::PathService::Get(base::DIR_EXE, &initial_prefs))
|
|
- return base::FilePath();
|
|
+ initial_prefs = base::FilePath("/etc/chromium");
|
|
return initial_prefs.AppendASCII(installer::kLegacyInitialPrefs);
|
|
}
|
|
|