Upstream added a `monai[ninja]` install option and a corresponding
`ninja = ` in `setup.cfg`, which broke a previous hack around
`setuptools` not detecting `ninja` correctly.
Split package into top-level Python library.
We need to propagate it just like any other package, otherwise
dependents cannot detect it during installation.
The __init__.py collide since it uses old-style namespaces so we get rid
of those. In the future we may need to extend the namespaces.
This was enough for my dependency opencensus-ext-azure.
Having it as a top-level Python is just common practice; there is no
good reason not to.
We are marking `resholve` itself with `meta.knownVulnerabilities`, and
overriding `resholve-utils` functions's `resholve` with
`meta.knownVulnerabilities = [ ]`.
This way, we can still use `resholve` at build-time without triggering
security warnings, however we can't instantiate `resholve` itself. See:
```
$ nix-build -A resholve
error: Package ‘resholve-0.8.4’ in /.../nixpkgs/pkgs/development/misc/resholve/resholve.nix:48 is marked as insecure, refusing to evaluate.
$ nix-build -A ix
/nix/store/k8cvj1bfxkjj8zdg6kgm7r8942bbj7w7-ix-20190815
```
For debugging purposes, you can still bypass the security checks and
instantiate `resholve` by:
```
$ NIXPKGS_ALLOW_INSECURE=1 nix-build -A resholve
/nix/store/77s87hhqymc6x9wpclb04zg5jwm6fsij-resholve-0.8.4
```
After libtiff's update to 4.5 in
4d4af86db6
hylafaxplus fails to build.
This is caused by libtiff 4.5 removing many exported symbols.
See this discussion for more details:
https://gitlab.com/libtiff/libtiff/-/issues/504
The next hylafaxplus relese will contain updated code such that
the missing code is simply added to the hylafaxplus codebase:
https://sourceforge.net/p/hylafax/HylaFAX+/2695/
To get hylafaxplus up and working again,
the commit at hand applies the corresponding patch.
Since Sourceforge doesn't permit to download patches
directly, we instead fetch the patch from Gentoo.
