This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-04
Channels
- # announcements (28)
- # asami (12)
- # aws (3)
- # babashka (69)
- # babashka-sci-dev (34)
- # beginners (52)
- # biff (3)
- # calva (20)
- # clj-kondo (4)
- # cljsrn (4)
- # clojars (1)
- # clojure (90)
- # clojure-czech (2)
- # clojure-europe (33)
- # clojure-nl (11)
- # clojure-norway (35)
- # clojure-seattle (1)
- # clojure-uk (5)
- # clojurescript (87)
- # cursive (10)
- # datascript (5)
- # datomic (35)
- # defnpodcast (1)
- # emacs (8)
- # events (4)
- # fulcro (1)
- # google-cloud (2)
- # graphql (2)
- # hispano (2)
- # honeysql (5)
- # hoplon (2)
- # hugsql (1)
- # jobs (7)
- # kaocha (9)
- # lsp (102)
- # meander (13)
- # observability (7)
- # off-topic (56)
- # overtone (2)
- # pathom (47)
- # podcasts (1)
- # rdf (30)
- # reagent (16)
- # reitit (1)
- # releases (2)
- # remote-jobs (26)
- # rewrite-clj (10)
- # tools-deps (4)
- # vim (5)
- # vscode (4)
- # xtdb (41)
@borkdude there may already be a good way to do this, but if not, what do you think about adding a download-pods
(or similar) subcommand for when you just want to pre-download your pods? i.e. bb download-pods
reads your :pods
from bb.edn
, downloads them to ~/.babashka/pods
, and exits. could also run describe on them and pre-cache that too I suppose (which is what I think will happen unless we take steps to prevent it for some reason).
or maybe prep-pods
I ran into a need for it (packaging pods as aws lambda layers) so I got it working locally. happy to put up a PR if you think it'd be generally useful
Perhaps! Haven't tried it yet. But I will.
yeah, bb --version
works for now. might want an explicit command at some point though. I could imagine recommending that people use bb --version
for this and then later deciding to optimize that out there since it doesn't need to do all of that work to print its version.
does deps.edn have a specific command to download deps? I thought they do it the same way: deps are always downloaded as an effect
either way bb -e nil
should do the trick as well. adding more subcommands: I want to hold off until that's really necessary
tools.deps used to do it the same way, then they added an explicit command for it
namely clojure -P
documented as: Prepare deps - download libs, cache classpath, but don't exec
but they still also download them on-demand as we should too
yeah, that makes sense
I can work up a PR for that (as I think it's already done save a small name change)
yes, it works
for deps and pods
CI failure looks intermittent, but let me know if not
@cap10morgan I had another idea. We could allow manifests to be directly fetched from https. So we could have:
{:pods {foo/bar {:manifest ""}}}
yeah, hmm...
wow, on neil main branch:
$ ./neil dep search cheshire
:lib cheshire/cheshire :version 5.10.2
:lib cambium/cambium.codec-cheshire :version 1.0.0
:lib com.vgeshel/cheshire :version 5.3.1.2
:lib metosin/muuntaja-cheshire :version 0.6.8
:lib fuziontech/ring-json-params :version 0.2.0
:lib org.clojars.doo/cheshire :version 2.2.3
:lib dsabanin/cheshire :version 5.1.2-SNAPSHOT
:lib sbtourist/cheshire :version 2.0.3_1
:lib cn.leancloud/cheshire :version 5.11.1-SNAPSHOT
:lib gorillalabs/muuntaja-cheshire :version 0.8.0
:lib com.github.youkale/cheshire :version 5.10.2-SNAPSHOT
:lib com.clojars.olimsaidov/cheshire :version 5.10.0
:lib org.clojars.vljosa/cheshire :version 5.5.1-SNAPSHOT
:lib io.xapix/cheshire :version 5.8.2-SNAPSHOT
:lib org.clojars.artmsh/cheshire :version 5.8.1-SNAPSHOT
:lib org.clojars.dlg/cheshire :version 5.8.2-SNAPSHOT
cc @teodorlu