@timothypratley: In the end I use something like you do to write in a different target directory. So, thanks !

I need some help understanding pods. I would have expected the following to return the modified pod environment, but I just get nil. Any help would be appreciated.

(set-env!
 :dependencies '[[org.clojure/clojure "1.8.0"]])

(defn get-pod-env []
  (let [env (update-in (get-env) [:dependencies] conj '[boot/core "2.6.0"])
        pod (boot.pod/make-pod env)]
    (boot.pod/with-eval-in pod
      (require '[boot.core :as boot])
      (boot/get-env))))

(println (get-pod-env))

@cal I would try to use pod/env

@richiardiandrea: Thanks. That seems to work.

I've gotten an error when running 'boot -u'

Seems to have disable my entire boot install and I can't seem to re-install. Anybody else seen this?

@anthony: looks like boot version is set to -vv somehow

it's trying to find that version

aha!

the boot version is set either via ~/.boot/boot.properties file, ./boot.properties, or the BOOT_VERSION environment variable

Thanks Micha!

a quick check you can do is move /.boot directory to like /.boot.bak

and see if that solves the problem

interesting issue though!

@anthony: if you would open a github issue i will implement some kind of sanity check there (if this is indeed the problem you're seeing)

Problem was excessive reliance on the command history! e.g. "boot show -U -vv" thanks for setting me straight.