New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fzf: fix vim plugin patch phase #40136
Conversation
During patch phase, the path to the fzf binary is overwritten in the vim plugin source. The sed expression doing this wasn't working because the fzf code changed in this commit: junegunn/fzf@02ceae1 making the patch useless. I fixed it and added a check to verify that the plugin was effecively patched to prevent this to happen in the future.
@GrahamcOfBorg eval |
@GrahamcOfBorg build fzf |
Success on x86_64-linux (full log) Attempted: fzf Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: fzf Partial log (click to expand)
|
Your change looks fine but there seems something else wrong with the install scripts (with or without this PR): Can you please check the build outputs (out, bin, man) to make sure their contents make sense. |
Success on x86_64-darwin (full log) Attempted: fzf Partial log (click to expand)
|
The problem here is that buildGoPackage puts source code into $out. Usually we only care about $bin for go packages. |
@ehmry @lethalman why do we install go source files? |
Since that seems to be a separate and more general issue, I'll merge this fix now. |
Motivation for this change
During patch phase, the path to the fzf binary is overwritten in the vim plugin source. The sed expression doing this wasn't working because the fzf code changed in this commit: junegunn/fzf@02ceae1 making the patch useless.
Things done
I fixed the sed expression and added a check to verify that the plugin was effectively patched to prevent this to happen in the future.
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)