6 comments

  • jpollock 4 minutes ago
    Isn't this the problem bazel's supposed to solve?
  • ramon156 1 hour ago
    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.
  • pseufaux 1 hour ago
    But isn't this built into uv already? Just point the sources table to GitHub.

    https://docs.astral.sh/uv/concepts/projects/dependencies/#pr...

    • mr_mitm 1 hour ago
      AFAIK uv installs python packages only. This fetches and runs binaries from Github.
      • pseufaux 1 hour ago
        Ah. Missed that. Thank you
  • figmert 1 hour ago
    But why? Mise does this and more. It can install binaries from github, gitlab, uv, npm, and many more.
    • nulldomain 36 minutes ago
      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.

  • droelf 38 minutes ago
    For pixi we also created a octoconda & a "github-releases" channel: https://prefix.dev/blog/octoconda-repackage-github-binary-re...
  • _ZeD_ 1 hour ago
    from TFA

        uv run ohbin run rg -- TODO src/
    
    yeaaah