diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2018-02-07 15:27:05 +0100 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2018-02-07 16:57:40 +0100 |
| commit | 8e70725077f750d8cc46611d6427dd0aa85a7e6e (patch) | |
| tree | e931f763be9b8cdf8d9a0cb264b6eac468c550d0 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 5e8ae8d5975ee93ce9bbf6c536591037cd518a66 (diff) | |
vim_configurable: enable overrides
Sometimes it's needed to override parts of `vim_configurable`, for
instance when using ENSIME (http://ensime.github.io/), in this case you
need a Python interpreter and the modules `sexpdata` and
`websocket_client`.
However overriding `vim_configurable` is quite hard as we run
`vimUtils.makeCustomizable` over the default comming from
`configurable.nix`. Therefore it's necessary to copy the code from
`all-packages.nix` and alter the parts you need: https://nixos.org/nix-dev/2017-April/023364.html
In order to simplify overriding `vim_configurable` I added an
`override` and an `overrideAttrs` function to `vimutils.makeCustomizable`
to ensure that the customization capabilities won't be lost after
altering the derivation.
Now it's possible to write expressions like this without evaluation
failures:
```
with pkgs;
let
vimPy3 = vim_configurable.override {
python = python3;
};
in vimPy3.customize { ... }
```
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
