| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We were adding this to the compilation of MacVim, but not to the
compilation of the separate Vim binary. We may not actually need it for
MacVim at all, but omitting it for the Vim binary meant our postInstall
phase would fail for some people.
Fixes #73514
|
|\ \
| |/
|/| |
vim: 8.1.2188 -> 8.1.2237
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|\
| |
| | |
macvim: Add sandboxProfile
|
| |
| |
| |
| |
| |
| | |
This allows full filesystem access except for Homebrew. This is because
we don't know where Xcode will be installed so we can't just whitelist
it and its dependencies.
|
|\ \
| |/
|/| |
macvim: fix compatibility with Xcode 11
|
| |
| |
| |
| |
| |
| | |
This fixes several Xcode 11 incompatibilities with MacVim, including an
issue where it wasn't inheriting the deployment target correctly to
begin with.
|
|/
|
|
|
|
|
| |
It seems that /usr/bin/ibtool marks stdin/stdout/stderr as nonblocking,
which can cause the subsequent build phase to fail when it tries to
write to stdout. I don't know why this problem just started happening
for me, but preventing ibtool from inheriting fds fixes the problem.
|
|\ |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
vim: 8.1.1547 -> 8.1.1866
|
| |
| |
| |
| |
| |
| |
| | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|\| |
|
| |\
| | |
| | | |
macvim: 8.1.1517 -> 8.1.1722
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
treewide replacement of
stdenv.mkDerivation rec {
name = "*-${version}";
version = "*";
to pname
|
|/
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
| |
|
|
|
|
|
|
| |
* treewide: remove unused variables
* making ofborg happy
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix up the macvim package to build again, with the latest snapshot. The
patchfile has been recreated by manually reapplying all of the changes
from the old patchfile, and the other changes in here were figured out
by trial and error (such as the need to unset `LD`).
Also tweak the package to use python37 by default, and add an option to
go back to python27 if desired.
Disable Sparkle so the user isn't prompted to update a readonly package.
|
|
|
|
|
|
|
| |
(cherry picked from commit 7c53ac01845a63f27ff5281c1b4c344eb406512a)
Picked from staging to master, as it's not really a big rebuild
and it includes an important security fix:
https://github.com/numirias/security/blob/master/doc/2019-06-04_ace-vim-neovim.md
|
|\ |
|
| |
| |
| |
| | |
builds on darwin
|
|/
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
|
|
|
| |
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
|
| |
Undefined symbols for architecture x86_64:
"_OBJC_CLASS_$_NSArray", referenced from:
objc-class-ref in os_macosx.o
ld: symbol(s) not found for architecture x86_64
|
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/vim/versions
|
|
|
|
|
|
| |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
vim
|
|
|
|
|
| |
Want to get this out of here for 18.09, so it can be deprecated
thereafter.
|
|\
| |
| | |
vim_configurable: fix darwin build with guiSupport
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using gtk + darwin support seems broken at the moment, we probably want
guiSupport = "carbon" instead but that doesn't work and something like
macvim is probably better for that. This fixes the build while keeping
guiSupport enabled which might be desirable for eg. +clientserver.
Fixes #45025
|
| |
| |
| |
| |
| | |
Using vim_configurable.override { guiSupport = "no"; } would still pull
in gtk2 as a dependency.
|
| | |
|
|/ |
|
| |
|