By the way, here's a working copy of the installation script I mentioned above (wrote a long time ago...): https://gist.github.com/zmwangx/7fbaafbb3e9f2833324c1ac6291b9ef1 Not completely polished but open to suggestions.
And here's how it works in practice:
```console
$ ./getgoogler.py
Downloading https://github.com/zmwangx/googler/releases/download/v3.8/googler-3.8.tar.gz to /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler.tar.gz ...
[76580/76580] Done.
Verifying SHA-256 checksum...
Extracting...
Installation prefix [/usr/local]: /tmp/googler
New files to be installed:
/tmp/googler/bin/googler
/tmp/googler/share/man/man1/googler.1
/tmp/googler/etc/bash_completion.d/googler-completion.bash
/tmp/googler/share/fish/vendor_completions.d/googler.fish
/tmp/googler/share/zsh/site-functions/_googler
Continue? [yes/no/quit]
> mkdir -p /tmp/googler/bin /tmp/googler/share/man/man1 /tmp/googler/etc/bash_completion.d /tmp/googler/share/fish/vendor_completions.d /tmp/googler/share/zsh/site-functions
> cp -f /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler-3.8/googler /tmp/googler/bin/googler
> cp -f /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler-3.8/googler.1 /tmp/googler/share/man/man1/googler.1
> cp -f /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler-3.8/auto-completion/bash/googler-completion.bash /tmp/googler/etc/bash_completion.d/googler-completion.bash
> cp -f /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler-3.8/auto-completion/fish/googler.fish /tmp/googler/share/fish/vendor_completions.d/googler.fish
> cp -f /var/folders/sk/v_4rk6391f58cvmc4h6fp5fr0000gn/T/tmpgoo3260v/googler-3.8/auto-completion/zsh/_googler /tmp/googler/share/zsh/site-functions/_googler
Installed googler.
> /tmp/googler/bin/googler --version
3.8
In the future, you may upgrade your googler installation by downloading and running the installer script again, or executing:
googler --upgrade
[WARNING] '/tmp/googler/bin' is not found in PATH. It is advised that you add it to PATH in the relevant shell runcoms.
```
> Googler project team needs to update the current version of the package on all the package sources.
That’s unrealistic.
(1) “The project team” is two people, on and off;
(2) Only Debian Developer (DDs) can update Debian packages;
(3) Debian is policy driven and (in)famous for outdated packages, I don’t think even DDs can just do as they wish. I’m unfamiliar with how Ubuntu update packages, only that they base their distro on Debian testing. Someone familiar with Ubuntu development is welcome to enlighten me on this topic.
If you think the situation is bad with disco, try to look at LTS (bionic at the moment) especially when they approach the end of the two years cycle. (I use Ubuntu LTS exclusively and feel the pain almost all the time.)
I've commented multiple times elsewhere (and maybe here too) that there's a fundamental disconnect between what Debian considers "stable" and what is actually stable or even usable for a certain class of software that requires regular tending. Debian considers old, battle-tested software to be stable. Except in the increasingly interconnected world, more and more software interacts with online services and old software may simply be broken. I don't know how to solve this problem.
---
Re `googler -u`: using this with a managed installation is not a good idea. It causes you to have a version that is different from what the package manger thinks you have, and future package manager "upgrades" may actually downgrade your installation. In fact I have a [make rule](https://github.com/jarun/googler#tips-for-packagers) for packagers to disable this mechanism, and at least I myself use it in the Homebrew package.
By the way, we actually discussed this Ubuntu/Debian-outdatedness problem a while back and I proposed just offering a installation script and be done with it.
Until then, I recommend [downloading a single file](https://github.com/jarun/googler#downloading-a-single-file).