If 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.
But isn't this built into uv already? Just point the sources table to GitHub.<p><a href="https://docs.astral.sh/uv/concepts/projects/dependencies/#project-dependencies" rel="nofollow">https://docs.astral.sh/uv/concepts/projects/dependencies/#pr...</a>
But 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.<p>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.
For pixi we also created a octoconda & a "github-releases" channel: <a href="https://prefix.dev/blog/octoconda-repackage-github-binary-releases" rel="nofollow">https://prefix.dev/blog/octoconda-repackage-github-binary-re...</a>
Isn't this the problem bazel's supposed to solve?
from TFA<p><pre><code> uv run ohbin run rg -- TODO src/
</code></pre>
yeaaah
[dead]