This fixes both `nix-shell` failing to eval with `nixUnstable`, as well
as ofborg's failure to eval on aarch64 due to passing an "unexpected
arg" (1112e3a8c8/ofborg/src/nix.rs (L334-L340)).
I will refactor NetSurf to make it more understandable and discoverable.
- First, it will be moved from misc/ to networking/browsers/, with all its
related libraries;
- Second, the expressions will be arranged in a flat directory.
vim_configurable and neovim have both supported a mechanism to build
them with a custom vimrc that supports plugins from Nix. This updates
MacVim to support the same sort of configuration using an expression
like
macvim.configure {
customRC = ''
# custom configuration goes here
'';
packages.myVimPackage = with pkgs.vimPlugins; {
start = [ youcompleteme fugitive ];
opt = [ phpCompletion elm-vim ];
}
}
Once configured, .override will allow for editing the configuration.
Like vim_configurable and neovim, configuring macvim does not require
rebuilding it. Also like them, configuring macvim turns off the user
vimrc file.
pyvips: init at 2.1.12
pyvips: init at 2.1.12
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/top-level/python-packages.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
pyvips: init at 2.1.12
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
once we've made some alterations to the source (which doesn't seem to have
been shipped in a ready-to-build state), we can use the funny custom build
system to build a wheel which can then be installed by the pipInstallHook.
running the tests is again annoying because an ini file setting pytest's
python_files parameter is missing, meaning we have to inject our own.
