Request for architecture-dependent install location

[tygoetsch]

Checklist

• I have read through the manual page (man fzf)
• I have searched through the existing issues
• For bug reports, I have checked if the bug is reproducible in the latest version of fzf

Output of fzf --version

0.58.0 (65db735)

OS

• Linux
• macOS
• Windows
• Etc.

Shell

• bash
• zsh
• fish

Problem / Steps to reproduce

This isn't quite a bug, but an uncommon use-case I think. I work on systems with different architectures (aarch64 and x86_64) that mount a shared filesystem for their home directories. The current install process for fzf is architecture-independent from what I can find, so fzf works only on the system that it was installed on, while it breaks on the other system due to the incompatible binaries being used.

I use vim-plug to manage my vim plugins, and I'm new to vimscript, so I don't know how to tell vim-plug to install to an architecture-dependent location. My workaround has been to remove fzf from my vim plugins and just manually clone/install it to arch-dependent directories and alter the .fzf.bash script to use the output of uname -m to determine which directory to source.

To Reproduce:

• Have access to 2+ systems with different architectures (aka x86_64 and aarch64) that mount a shared filesystem for their $HOME directory
• Login to one of the systems
• git clone fzf to ~/.fzf and cd to ~/.fzf
• ./install -y
• Logout of that system and into the other one
• Source your .bashrc if it hasn't been done already
• Error Output:
  bash: /users/$USER/.fzf/bin/fzf: cannot execute binary file: Exec format error

[junegunn]

I use vim-plug to manage my vim plugins

Do you use vim-plug to install fzf? Or you manually install it on the shell? How does your Plug command for fzf look like?