Found with `fd \\.patch$ pkgs/ -x bash -c 'rg -F "{/}" pkgs/ -q || echo {}'``
We're running more and more into patches fetched via `applyPatches`, for the next PR i'll script something to account for that.
- Patch has been merged, fetch merged one & update comment (hash is unchanged, checked)
- We now have a CMake modern enough for pkg_get_variable DEFINE_VARIABLES, use it
- substituteInPlace --replace is deprecated
- with lib; in meta is frowned-upon
LAL manages desktop file parsing for various parts of the Lomiri environment. It also handles turning them into SystemD services tracked in the background.
And due to how things work one, it's code is also SystemD-launched by itself.
When we package applications with desktop files, we don't want the Exec values to be absolute, so we patch out absolute paths.
Without absolute paths, PATH is expected to have the path to the executables. But our PATHs don't always contain i.e. /run/current-system/sw/bin.
Services launched by SystemD are one such instance. If LAL code is run under SystemD's restricted reduced PATH, then it fails to find the requested executables.
This is what happens to content-hub, and it causes all transfer requests to be met with an immediate "could not launch peer"-like error, and a transfer being stuck halfway.
To work around this (I wouldn't call this a real solution?), patch LAL code to:
- also propagate whatever PATH it currently *does* have to its launched applications
- postfix the PATH it has with /run/current-system/sw/bin, to give it a decent fallback
These changes allow for lomiri-filemanager-app to be launched via a content-hub request from lomiri-system-settings (i.e. the background selection).
The UserMetrics service expects AppArmor to be available, and its database access breaks when that's not the case.
Details: https://gitlab.com/ubports/development/core/libusermetrics/-/issues/8
We need to set an envvar for it to work AppArmor-less, but that requires system config knowledge.
Solve this by telling the D-Bus service to look for & launch a systemd service, which we will later create in the Lomiri module.
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
Going `${CMAKE_INSTALL_BINDIR}/../` looks weird. Derivations that want them in a non-`out` output can just set the `QMLFILES_DESTINATION` CMake flag as needed.
Co-authored-by: rewine <luhongxu@deepin.org>
We sometimes place QML modules into the bin output of derivations. Using CMAKE_INSTALL_BINDIR and backtracking from it
will ensure that the modules will end up under the bin output prefix, if it is enabled.
