diff options
| author | Jan Tojnar <jtojnar@gmail.com> | 2022-03-28 15:42:41 +0200 |
|---|---|---|
| committer | Jan Tojnar <jtojnar@gmail.com> | 2022-04-10 03:54:39 +0200 |
| commit | e8c84f90ed0f4f0f880d1217b26d6c026ec43a2f (patch) | |
| tree | 1fcc7a9ea23bfb15957bd3d1ae7d5b8a844ec4aa /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 7de3765a5dbf16554abccd9bf3c4a7743baa493c (diff) | |
chromium: remove deprecated libgnome-keyring dependency
libgnome-keyring has been deprecated for a long time.
It has been superseded by libsecret, which allows access to not only
GNOME Keyring secret manager but any other service implementing
the Secret Service D-Bus API.
In fact Chromium links against libsecret when use_glib is enabled:
https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/BUILD.gn;l=142;drc=35be6215ec8f09e50176f36753c68f26c63d1885
And use_glib is on by default on Linux:
https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/BUILD.gn;l=142;drc=35be6215ec8f09e50176f36753c68f26c63d1885
Unfortunately, Chromium is vendoring libsecret:
https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/BUILD.gn;l=187;drc=35be6215ec8f09e50176f36753c68f26c63d1885
We need to disable the flag explicitly, since it is enabled by default:
https://source.chromium.org/chromium/chromium/src/+/main:components/os_crypt/features.gni;l=11;drc=35be6215ec8f09e50176f36753c68f26c63d1885
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions