JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
8cc8b3b235
nixpkgs/pkgs/tools/misc/fzf/default.nix

67 lines
1.8 KiB
Nix
Raw Normal View History

fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
{ lib, buildGoModule, fetchFromGitHub, writeText, runtimeShell, ncurses, }:
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
buildGoModule rec {
pname = "fzf";
fzf: 0.19.0 -> 0.20.0
2019-12-21 03:30:39 +00:00
version = "0.20.0";
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
Moving from fetchgit generated by go2nix to fetchFromGitHub where rev is a tag
2016-06-06 11:26:56 +01:00
src = fetchFromGitHub {
owner = "junegunn";
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
repo = pname;
rev = version;
fzf: 0.19.0 -> 0.20.0
2019-12-21 03:30:39 +00:00
sha256 = "02zy3c4k84rzqdkaf04idbj10v286hi0ix1xl2qsz1wrblh168w8";
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
};
fzf: 0.18.0 -> 0.19.0
2019-12-03 18:18:33 +00:00
modSha256 = "12lnv8b96adpcg9qfizcyd9nxz590nxd82xch6ij719zlqyps143";
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
outputs = [ "out" "man" ];
fzf: install manpage Closes #21706
2017-01-06 09:27:35 +00:00
fzf: add fish hook for NixOS
2017-04-04 00:30:08 +01:00
fishHook = writeText "load-fzf-keybindings.fish" "fzf_key_bindings";
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
buildInputs = [ ncurses ];
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
# The vim plugin expects a relative path to the binary; patch it to abspath.
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
patchPhase = ''
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
sed -i -e "s|expand('<sfile>:h:h')|'$out'|" plugin/fzf.vim
fzf: fix vim plugin patch phase 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: https://github.com/junegunn/fzf/commit/02ceae15a235de6b5cd2aca9de070fb3fff78e5b 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.
2018-05-07 04:42:05 +01:00
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
if ! grep -q $out plugin/fzf.vim; then
echo "Failed to replace vim base_dir path with $out"
exit 1
fzf: fix vim plugin patch phase 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: https://github.com/junegunn/fzf/commit/02ceae15a235de6b5cd2aca9de070fb3fff78e5b 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.
2018-05-07 04:42:05 +01:00
fi
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
'';
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
doCheck = true;
fzf: add fish hook for NixOS
2017-04-04 00:30:08 +01:00
preInstall = ''
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
mkdir -p $out/share/fish/{vendor_functions.d,vendor_conf.d}
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
cp shell/key-bindings.fish $out/share/fish/vendor_functions.d/fzf_key_bindings.fish
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
cp ${fishHook} $out/share/fish/vendor_conf.d/load-fzf-key-bindings.fish
fzf: add fish hook for NixOS
2017-04-04 00:30:08 +01:00
'';
fzf: fix cycle in bin output
2016-09-14 21:29:08 +01:00
postInstall = ''
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
cp bin/fzf-tmux $out/bin
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
fzf: install manpage Closes #21706
2017-01-06 09:27:35 +00:00
mkdir -p $man/share/man
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
cp -r man/man1 $man/share/man
fzf: add script for finding 'share' folder So that helper scripts can be easily sourced in interactive shell configuration. `autojump` package was already present and had the same requirements for findind a `share` folders, so I took an inspiration there. I beleive this is a better alternative to: - https://github.com/NixOS/nixpkgs/pull/25080 - https://github.com/NixOS/nixpkgs/pull/27058 Replacing `$out/share/shell` with `$bin/share/fzf` was necessary to prevent dependency loop in produced derivations.
2017-07-28 10:42:28 +01:00
fzf: fix unstable vim plugin path exclude version number from vim plugin path
2019-11-28 13:54:24 +00:00
mkdir -p $out/share/vim-plugins/${pname}
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
cp -r plugin $out/share/vim-plugins/${pname}
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
fzf: fix patch for vim plugin; enable tests; avoid direct $src… (#79575) It was previously referencing `$bin`, but this package no longer produces a `bin` output, just `out` and `share`. Updated to make the comparison check a bit more robust. Also updated to avoid direct dependency on the `$src` directory out of the nix store, instead using the processed src setup in the unpackPhase. This provides a cleaner abstraction between the build/install phase and the input src phase, and avoids an unnecessary dependency on whether the source disted tarball comes from `fetchFromGitHub` (in which case it's an unpacked directory) or something like `fetchurl`. In either case, stdenv is responsible for processing the input `src` and setting up a clean build dir for us, so we should use that. This produces an equivalent directory tree, except that the vim plugin is no longer broken.
2020-02-09 23:43:22 +00:00
cp -R shell $out/share/fzf
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
cat <<SCRIPT > $out/bin/fzf-share
treewide: use runtimeShell instead of stdenv.shell whenever possible 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.
2019-02-26 11:45:54 +00:00
#!${runtimeShell}
fzf: add script for finding 'share' folder So that helper scripts can be easily sourced in interactive shell configuration. `autojump` package was already present and had the same requirements for findind a `share` folders, so I took an inspiration there. I beleive this is a better alternative to: - https://github.com/NixOS/nixpkgs/pull/25080 - https://github.com/NixOS/nixpkgs/pull/27058 Replacing `$out/share/shell` with `$bin/share/fzf` was necessary to prevent dependency loop in produced derivations.
2017-07-28 10:42:28 +01:00
# Run this script to find the fzf shared folder where all the shell
# integration scripts are living.
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
echo $out/share/fzf
fzf: add script for finding 'share' folder So that helper scripts can be easily sourced in interactive shell configuration. `autojump` package was already present and had the same requirements for findind a `share` folders, so I took an inspiration there. I beleive this is a better alternative to: - https://github.com/NixOS/nixpkgs/pull/25080 - https://github.com/NixOS/nixpkgs/pull/27058 Replacing `$out/share/shell` with `$bin/share/fzf` was necessary to prevent dependency loop in produced derivations.
2017-07-28 10:42:28 +01:00
SCRIPT
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
chmod +x $out/bin/fzf-share
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
'';
fzf: 0.13.2 -> 0.13.3 (#17013)
2016-07-18 05:36:35 +01:00
fzf: 0.17.5 -> 0.18.0
2019-07-10 17:36:06 +01:00
meta = with lib; {
homepage = "https://github.com/junegunn/fzf";
fzf: 0.13.2 -> 0.13.3 (#17013)
2016-07-18 05:36:35 +01:00
description = "A command-line fuzzy finder written in Go";
license = licenses.mit;
treewide: update which packages I'm currently maintaining Idea shamelessly stolen from 4e60b0efae56cc8e1a8a606a5a89462c38aba305. I realized that I don't really know anymore where I'm listed as maintainer and what I'm actually (co)-maintaining which means that I can't proactively take care of packages I officially maintain. As I don't have the time, energy and motivation to take care of stuff I was interested in 1 or 2 years ago (or packaged for someone else in the past), I decided that I make this explicit by removing myself from several packages and adding myself in some other stuff I'm now interested in. I've seen it several times now that people remove themselves from a package without removing the package if it's unmaintained after that which is why I figured that it's fine in my case as the affected pkgs are rather low-prio and were pretty easy to maintain.
2019-12-26 14:13:48 +00:00
maintainers = with maintainers; [ filalex77 ma27 ];
fzf: 0.13.2 -> 0.13.3 (#17013)
2016-07-18 05:36:35 +01:00
platforms = platforms.unix;
};
fzf: application extracted from goPackages
2016-06-02 20:21:45 +01:00
}
Reference in New Issue Copy Permalink