Official Ubuntu `apt` repositories have outdated version

[SarveshMD]

• [x] I have read through the manual page (man fzf)
• [x] I have the latest version of fzf
• [x] I have searched through the existing issues

Info

• OS
  • [x] Linux
  • [ ] Mac OS X
  • [ ] Windows
  • [ ] Etc.
• Shell
  • [x] bash
  • [x] zsh
  • [x] fish

Problem / Steps to reproduce

As the Installation Instructions suggests, when we use sudo apt-get install fzf to install fzf, we get fzf v0.21.0-1. This version was released on 13rd March 2020. There have been 289 commits to master since that release. So, the users who installed fzf using sudo apt install fzf or sudo apt-get install fzf are using an outdated version of fzf. This could be solved by creating a PPA to contain the latest version of fzf and changing the installation instructions to add that PPA using apt-add-repository and then installing fzf, to get the latest version of fzf.
This issue is not shell specific since everyone who installed using apt or apt-get would have this issue. I selected I have the latest version because I cloned the repository and used the install script. This can be done too, but using a PPA is much more convenient to users.

[karambaq]

Any news?

[junegunn]

I'm not a Ubuntu user, so I don't have incentive to create and maintain a PPA unless someone offers me some big money 😄

Alternatively, you can instead:

• Use Homebrew
• Install Go and run go install github.com/junegunn/fzf@latest
  • Shell integration scripts are now embedded in the binary, and with native tmux integration coming, the single fzf binary is all you're going to need.

[AllanDaemon]

I'm not a Ubuntu user, so I don't have incentive to create and maintain a PPA unless someone offers me some big money 😄

Alternatively, you can instead:

• Use Homebrew

• Install Go and run go install github.com/junegunn/fzf@latest

  • Shell integration scripts are now embedded in the binary, and with native tmux integration coming, the single fzf binary is all you're going to need.

I'm willing to create a PR to add a Github Workflow to build and upload it to a PPA. But I don't want to own it. Would you accept @junegunn if I setup and create it, then pass the PPA account to you, maybe share the access, but keep it officially owned (as in passwords and access) by the project?

I should do it anyways at least in some fork so I keep the updates automatically in my system. If you accept the PR back would be awesome.

[junegunn]

If all I have to do is to open up an account and wire it up to the GitHub workflow, I can do that. But I know nothing about PPA, so I would need your assistance throughout the process.

[SarveshMD]

It's good to see this issue is being worked on after 3 years 😆.