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.
Also, move to fetch src off the official `beancount` github org and update
dependencies. I've run this on my ledger file and it seems to work without issue.
Changes are minor - I ended up just patching the ssl certs at the root
file, rather than trying to keep up with the various darwin changes.
The externalnetwork test helper location changed, to so I had to update
that patch as well.
- Add xcbuild as propagatedBuildInput on darwin https://github.com/golang/go/commit/7e25bdba5e79d223566745fca2410f725a6dedda
Our patchShebangs expect coreutils stat instead of busybox stat.
This broke patching the dispatch script. By enabling strict
dependencies and using explicit --host parameter we not only
avoid cross-compiling breackages but also work around this problem.
Signed-off-by: Jörg Thalheim <joerg@thalheim.io>
Socket.IO and Engine.IO protocols are not backwards-compatible and major
versions of the client and server need to be coordinated. It's therefore useful
to have python-socketio 4.x available.
Socket.IO and Engine.IO protocols are not backwards-compatible and major
versions of the client and server need to be coordinated. It's therefore useful
to have python-engineio 3.x available for use with python-socketio 4.x.
Sandro