From 74b8b4cbe3c0aaa1202566a9299c1e1db0f1b1ff Mon Sep 17 00:00:00 2001 From: Lily Ballard Date: Fri, 24 Oct 2025 00:27:07 -0700 Subject: [PATCH] macvim: remove postPatch phase for Sparkle.framework MacVim itself now has a script that deletes Sparkle.framework from the build result, so we don't need to avoid copying it anymore. --- pkgs/applications/editors/vim/macvim.nix | 8 -------- 1 file changed, 8 deletions(-) diff --git a/pkgs/applications/editors/vim/macvim.nix b/pkgs/applications/editors/vim/macvim.nix index 91cce5f34de5..1a71a1f9daf9 100644 --- a/pkgs/applications/editors/vim/macvim.nix +++ b/pkgs/applications/editors/vim/macvim.nix @@ -106,14 +106,6 @@ stdenv.mkDerivation (finalAttrs: { "--disable-sparkle" ]; - # Remove references to Sparkle.framework from the project. - # It's unused (we disabled it with --disable-sparkle) and this avoids - # copying the unnecessary several-megabyte framework into the result. - postPatch = '' - echo "Patching file src/MacVim/MacVim.xcodeproj/project.pbxproj" - sed -e '/Sparkle\.framework/d' -i src/MacVim/MacVim.xcodeproj/project.pbxproj - ''; - # This is unfortunate, but we need to use the same compiler as Xcode, but Xcode doesn't provide a # way to configure the compiler. We also need to pull in lib/include paths for some of our build # inputs since we don't have cc-wrapper to do that for us.