This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-29
Channels
- # adventofcode (7)
- # announcements (11)
- # beginners (76)
- # boot (3)
- # calva (139)
- # cider (24)
- # clara (2)
- # cljdoc (11)
- # cljs-dev (90)
- # cljsjs (1)
- # cljsrn (3)
- # clojure (98)
- # clojure-austin (2)
- # clojure-brasil (2)
- # clojure-dev (16)
- # clojure-europe (3)
- # clojure-italy (55)
- # clojure-nl (37)
- # clojure-sweden (11)
- # clojure-uk (40)
- # clojurebridge (1)
- # clojurescript (107)
- # core-logic (10)
- # cursive (34)
- # data-science (9)
- # datascript (19)
- # datomic (48)
- # emacs (6)
- # figwheel (13)
- # figwheel-main (3)
- # fulcro (67)
- # jobs (1)
- # juxt (4)
- # lumo (8)
- # mount (1)
- # off-topic (29)
- # onyx (1)
- # reagent (7)
- # reitit (3)
- # ring-swagger (5)
- # shadow-cljs (39)
- # spacemacs (5)
- # tools-deps (1)
Has anyone looked into what it would take to make Boot play well with Nix, in the "let Nix manage downloading and caching" sense of "play well"? Nixpkgs has a boot package, but it doesn't appear that it can be used in the sandboxed, network-free build environment where Nix derivations are built.
...generally, running a build in Nix means giving Nix a list of everything that needs to be retrieved from a network -- whether that's a git checkout, a HTTP download, the result of a different set of build operations on software previously so downloaded, or whatever else -- ahead of time, receiving a list of paths with locations at which those items can be found (typically hash-addressed locations in a read-only shared store); and performing one's build steps in an isolated environment where only those declared inputs are available. (Oh -- and in typical "pure" mode, network sources can only be used when checksums for the downloaded content are known ahead-of-time).