This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-19
Channels
- # ai (4)
- # announcements (1)
- # babashka (6)
- # beginners (31)
- # biff (1)
- # calva (11)
- # cider (9)
- # clerk (6)
- # clojure (40)
- # clojure-europe (49)
- # clojure-nl (1)
- # clojure-norway (30)
- # clojurescript (17)
- # conjure (1)
- # core-async (2)
- # datalevin (28)
- # emacs (1)
- # events (4)
- # fulcro (7)
- # gratitude (1)
- # guix (4)
- # hyperfiddle (19)
- # juxt (10)
- # luminus (4)
- # malli (4)
- # missionary (11)
- # nbb (3)
- # pedestal (7)
- # reagent (27)
- # reitit (2)
- # releases (1)
- # shadow-cljs (32)
- # tools-deps (6)
- # xtdb (5)
I'm I correct that the best way to compose version-locked packages (e.g. java, Nodejs) is via Guix shell? So, for example: > guix shell openjdk@11 nodejs@12 -- bash Follow-up questions... using Guix like this would supplant the need for nvm, right? Meanwhile, java doesn't seem to have a good way to switch versions on a per-project (file directory) basis, or is there one?
I'm on the clock so apologies in advance for this incomplete response: I think you can set up each project with a manifest file to specify exact versions and packages per each.
yes, but IMO, guix currently does not have a sistem to work with multiple versions at the same time. Debian has alternatives for example https://wiki.debian.org/DebianAlternatives . nvm, sdk are designed with this purpose in mind. I don't know os such a thing in guix per se. As a package manager you can choose to support multiple versions at the same time, but I believe end user does not have a way to specify which version to use (except maybe JAVA_HOME or similar, but not sure how this works in guix ).