But also tldr, lazysql, lazygit, croc, bit, viddy, up, fd, lsd, bat, fzf, rg, difft, certinfo, sops, age, gomuks, gotty, humanlog, jira, plow, pngsource, reflex, jq, gojq, jqp, mlr, fx, hugo, syncthing, minikube, dog, sd, navi, grex, zellij, xplr, gping, dust, dua, duf, xh, frp, rclone, etc.
While gogo supports running directly against a Github repo (gogo <pkg> or gogo <user>/</pkg>), you should regularly update its list of pre-configured packages:
By default, it will be created in your user config directory, under gogo. You can specify a different location by running gogo -config <path>.
If you are running this tool as an anonymous user, you will be able to perform up to 60 queries per hour. If should be enough for many use cases.
A: This is a known issue. The binaries I fetch are built for more recent versions of glibc than the one you have. You can either build them yourself, or reach out to the maintainer of the project to build them for your architecture.