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.
The project switched to pyproject, allowing the use of
`buildPythonApplication` instead of `mkDerivation`.
Some of the modules listed as dependencies but shipping with Python
itself had to be patched out.
* matrix-commander: init
* matrix-commander: cleanups & potential dep fixes
apply most SuperSandro2000's review comments;
used python3.withPackages -- this might be the correct
way to get runtime python dependencies to work even
when matrix-commander is a dependency of another packages
(as opposed to testing in nix-shell). I'm not sure though.
aiofiles seemed to be a missing runtime dependency when called
from another (nix-packaged, jvm-based) app -- there was an
import error without it.
cacerts might require explicit pinning, as described here:
https://gist.github.com/CMCDragonkai/1ae4f4b5edeb021ca7bb1d271caca999
(relevant snippet: wrapProgram $out/bin/program \
--set SSL_CERT_FILE "${cacert}/etc/ssl/certs/ca-bundle.crt"
)
* add runHook {pre,post}Install
(suggested by r-rmcgibbo)
* add link to github issue re gpl3{Only,Plus}
* Update pkgs/applications/networking/instant-messengers/matrix-commander/default.nix
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>