diff options
| author | Elias Probst <mail@eliasprobst.eu> | 2021-01-03 23:24:59 +0100 |
|---|---|---|
| committer | Peter Hoeg <peter@hoeg.com> | 2021-02-17 09:06:14 +0800 |
| commit | aec54bddb805fe1199e2a47895ceb09f94c75e17 (patch) | |
| tree | a33555630c5b1da76b863d11942e4fe82bfee14c /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 290fdcf76f0aacf863d8b9ac9f59ac4a06509949 (diff) | |
kinfocenter: fix symlink to systemsettings5
As `kinfocenter`'s implementation consists of only KCMs, which are
actually just displayed using `systemsettings5`' KCM shell, the
`kinfocenter` binary is just a symlink to `systemsettings5`.
In traditional FHS environments, having a relative symlink to the
`systemsettings5` binary within the same `bin/` directory works just
fine, whereas this is broken on NixOS where `systemsettings5` resides in
a completely different `bin/` directory of the corresponding store item.
Usually CMake's `find_package` should be able to locate the
`systemsettings5` binary, but fails for reasons unknown to do so on
NixOS - so for now fixing the symlink manually as part of the `preFixup`
phase will do the job of making `kinfocenter` work again.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions