This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-25
Channels
- # babashka (77)
- # beginners (107)
- # calva (20)
- # cider (2)
- # clj-kondo (7)
- # clojure (63)
- # clojure-australia (2)
- # clojure-europe (75)
- # clojure-germany (10)
- # clojure-italy (3)
- # clojure-nl (3)
- # clojure-serbia (15)
- # clojure-spain (2)
- # clojure-uk (24)
- # clojurescript (54)
- # clojureverse-ops (3)
- # cursive (20)
- # datahike (4)
- # datalog (5)
- # datascript (8)
- # datomic (13)
- # emacs (2)
- # fulcro (1)
- # graalvm (2)
- # instaparse (1)
- # jobs (2)
- # luminus (1)
- # malli (7)
- # off-topic (28)
- # pathom (6)
- # pedestal (2)
- # re-frame (5)
- # reagent (9)
- # remote-jobs (4)
- # rewrite-clj (4)
- # ring (19)
- # shadow-cljs (2)
- # spacemacs (2)
- # sql (10)
- # tools-deps (6)
- # xtdb (12)
I found that ~/.gitlibs/_repos/<repo-path>/worktrees/<sha>/gitdir
files contain absolute paths to subfolders under ~/.gitlibs/libs/
. This seems to result in conflicts when I want to share my ~/.gitlibs
between my physical machine (mac) where I conduct most of my dev work and a docker container (linux, different user etc.) which is necessary for a special project I work on.
Is there any nice way around this? For now I just let git deps be downloaded every time the container starts. Perhaps I can set up another local gitlibs folder which would be container-only?
I might have just rubber -ed myself using this channel. I can mount different, image/project-specific folders into
~/.gitlibs
and .cpcache
You can set the GITLIBS env var to say where the root is