Ohbin – uv wrapper for installing tools from GitHub
1–10 of 20 posts
Re: Ohbin – uv wrapper for installing tools from GitHub
#2from TFA
uv run ohbin run rg -- TODO src/
Re: Ohbin – uv wrapper for installing tools from GitHub
#3If you're going to let an LLM write docs, at least let them write to the target of the dev. this README seems more internal, or more like a pitch, i suppose. It's weird.
Re: Ohbin – uv wrapper for installing tools from GitHub
#4But isn't this built into uv already? Just point the sources table to GitHub.
https://docs.astral.sh/uv/concepts/projects/dependencies/#pr...
Re: Ohbin – uv wrapper for installing tools from GitHub
#5But isn't this built into uv already? Just point the sources table to GitHub. https://docs.astral.sh/uv/concepts/projects/dependencies/#pr...
AFAIK uv installs python packages only. This fetches and runs binaries from Github.
Re: Ohbin – uv wrapper for installing tools from GitHub
#6But why? Mise does this and more. It can install binaries from github, gitlab, uv, npm, and many more.
Re: Ohbin – uv wrapper for installing tools from GitHub
#7Re: Ohbin – uv wrapper for installing tools from GitHub
#8For pixi we also created a octoconda & a "github-releases" channel: https://prefix.dev/blog/octoconda-repackage-github-binary-re...
Re: Ohbin – uv wrapper for installing tools from GitHub
#9But why? Mise does this and more. It can install binaries from github, gitlab, uv, npm, and many more.
Agreed, this looks like a far more limited mise alternative that still requires a completely different tool to run.
Not sure if I'm misunderstanding the private binaries concept - what advantage does gzipping and encrypting the binary and putting it in an unlisted gist have over just storing a release in a private git repo only I can access with my PAT or key? Seems needlessly complicated.
Re: Ohbin – uv wrapper for installing tools from GitHub
#10Isn't this the problem bazel's supposed to solve?