This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-20
Channels
- # aleph (11)
- # announcements (3)
- # babashka (35)
- # babashka-sci-dev (28)
- # beginners (29)
- # calva (51)
- # cider (33)
- # clj-kondo (26)
- # clj-on-windows (1)
- # clojure (40)
- # clojure-austin (1)
- # clojure-europe (47)
- # clojure-nl (9)
- # clojure-norway (7)
- # clojure-uk (5)
- # clojurescript (69)
- # conjure (30)
- # cursive (7)
- # data-science (9)
- # datomic (2)
- # etaoin (10)
- # events (2)
- # fulcro (1)
- # graalvm (1)
- # gratitude (6)
- # helix (16)
- # honeysql (20)
- # hyperfiddle (14)
- # inf-clojure (2)
- # jobs (1)
- # jobs-discuss (12)
- # kaocha (9)
- # leiningen (2)
- # lsp (4)
- # malli (8)
- # music (9)
- # off-topic (12)
- # pathom (10)
- # portal (14)
- # practicalli (15)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (4)
- # sci (37)
- # shadow-cljs (16)
- # sql (8)
- # tools-deps (6)
- # vim (6)
- # xtdb (21)
@thiagokokada https://twitter.com/k0kada/status/1527597540681596930 Where do those binaries get built for macOS aarch64, I imagine someone must run a machine somewhere for this to work right?
On hydra, that is the nixpkgs CI/CD: https://hydra.nixos.org/build/177587246
What is the fastest way for me to download a binary for babashka 0.8.2 from this and redistribute it?
There should be a less convoluted way, but what I got:
• Go to this link and get the Output store paths
(in this example it is /nix/store/i0h0cs4kadrpfass23rd37g7wnw76b0s-babashka-0.8.2
): https://hydra.nixos.org/build/177587246#tabs-details
• nix copy --from
• cp /nix/store/i0h0cs4kadrpfass23rd37g7wnw76b0s-babashka-0.8.2/bin/bb .
e.g. if I want to do a release, and upload the binary to Github releases, how long do I wait?
Once the PR is merged, it will enter on the master
branch and eventually it will be evaluated by a Hydra Job.
I got this from the staging-next
channel, but a better one would be from nixpkgs-unstable
I wouldn't say this is the best way to distribute the binaries, but it can be an alternative until you have a proper CI
We don't have any nixos instructions here: https://github.com/babashka/babashka#installation Perhaps we can make them and then point m1 users to that
Well, like I said, this is not a proper CI, and it only works in this specific case because macOS builds on GraalVM are always static
yes, I mean, if m1 users really want the m1 binary they can use nix. So we should document where to start with that
Let me see if I can make a somewhat user friendly way to use babashka with nix, even if "technically" wrong
We can make a separate page in doc
about nix perhaps with a longer, more correct instructions for people who want to seriously use it
Yeah, I think it makes sense, but I also think that some people just want something to use