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.
Heck, mise has an HTTP backend that can install binaries from any URL. I use this to manage Atlassian CLI, whose official Windows binary is not on winget.
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.
I am more used to uv than pixi or mise so it would be an easier addition to my workflow.
However I do think it would probably be nicer if this kind of approach used conda packages as a source of truth. So kind of like pixi but without pixi!
[delayed]
This is pretty cool, I'm doing something similar for binaries I use on my computer - https://github.com/chasen-bettinger/conf/blob/main/binaries....
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 why? Mise does this and more. It can install binaries from github, gitlab, uv, npm, and many more.
Heck, mise has an HTTP backend that can install binaries from any URL. I use this to manage Atlassian CLI, whose official Windows binary is not on winget.
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.
mise ftw!
But 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.
Ah. Missed that. Thank you
This is pretty neat.
I am more used to uv than pixi or mise so it would be an easier addition to my workflow.
However I do think it would probably be nicer if this kind of approach used conda packages as a source of truth. So kind of like pixi but without pixi!
For pixi we also created a octoconda & a "github-releases" channel: https://prefix.dev/blog/octoconda-repackage-github-binary-re...
from TFA
yeaaahIsn't this the problem bazel's supposed to solve?
there are a few projects not using bazel