diff options
| author | Thiago Kenji Okada <thiagokokada@gmail.com> | 2022-04-16 12:37:37 +0100 |
|---|---|---|
| committer | Thiago Kenji Okada <thiagokokada@gmail.com> | 2022-04-16 12:59:54 +0100 |
| commit | 5c9a8665511a7757aac91b020c8b7162d7cde479 (patch) | |
| tree | d565a860229ec0d37d1c780f819295a71ef55114 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | f6996978579f1269b58d741506a614a4fb1817ff (diff) | |
graalvmXX-ce: add sourcesPath parameter
In #168816, we removed support for Python/Ruby/WASM to reduce the
support burden of GraalVM languages that, arguably, are not really being
used.
However, the way that `pkgs.graalvmCEPackages.mkGraal` function works
right now doesn't allow passing a custom sources file, that would allow
someone to compile GraalVM with the additional products (e.g.: Python).
This PR adds this possibility.
So if someone wants to create a custom graalvm11-ce derivation with
Python support, for example, they can do something like this:
```nix
let
graalvm11-ce-custom = pkgs.graalvmCEPackages.mkGraal {
config = {
x86_64-linux = {
products = [ "graalvm-ce" "python-installable-svm" ];
arch = "linux-amd64";
};
};
defaultVersion = "22.0.0.2";
javaVersion = "11";
platforms = "x86_64-linux";
sourcesPath = /home/someone/graalvm11-ce-sources.json;
};
in
{
environment.systemPackages = [ graalvm11-ce-custom ];
}
```
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
