How to confuse yourself: in Ubuntu bash on Windows (via WSL 1), type scoop update clojure, and wonder why, after completing successfully, when you type clojure -Sdescribe it shows the version you previously had installed...

...then switch to PowerShell and run clojure -Sdescribe and realize that it was updated: Windows figured out scoop was a Windows command, even tho' you typed it into Ubuntu, and ran it on Windows anyway... 👀

so the command here: clj -A:pack mach.pack.alpha.jib --image-name --image-type registry -m my.main from https://github.com/juxt/pack.alpha. seems to suggest that by passing -m its going to record that as the main namespace. but whats happening is that its "running" that namespace. which makes sense given that passing -m to clj does just that. what i'm i missing?

hmmm

actually that might not be the issue. is mach.pack.alpha.jib a script/function im passing clj and the rest are the args?

yea, thats probably right

my issue was that i told the pack alias to run the main function.

I tried on an Ubuntu 16.04 Linux machine (freshly installed, latest updates from Canonical as of today), to install Homebrew for Linux, then brew install clojure. It installed the latest version 1.10.1.483 which brought up a REPL just fine. The Linux VM I tested on had no previous installation of ruby, clojure, nor Java. brew install clojure installed them all automatically as dependencies, choosing AdoptOpenJDK 8 for the JDK (plus some things that surprised me, but didn't hurt -- e.g. gcc seemed weird)

Probably a very-FAQ, but googling didn't help me at all. how do teams deal with sharing deps.edn files that use :local/root? one option is to symlink the common code folder on everyone's machines, but i'm wondering if the lib itself supports something out of the box

It depends 🙂

If they're released separately, then I wouldn't use :local/root

this is just to support a short period of active new development

release will use the usual s3 maven repo nonsense, until we can get everything transitioned to deps, and then we'll use the git sha thing

is there inbuilt capability to resolve local relative paths, or is symlinks the way?

just as a workflow thing for what I do: as someone doing multi-repo development I personally setup aliases in my ~/.clojure/deps.edn file.

Some of my colleagues don't do any cross-development, so they don't have to care. When I do the cross development, I just activate the extra profile(s) on launch.

relative paths do work though.

ah, i tried relative to home ~/Code/... but not relative to folder ../..., going to try that now

thanks Dominic!

Yeah, no support for ~. I think it's been discussed & rejected. .. works though, used heavily in Edge.

nice!

if your projects deps.edn uses git/url to point at another project, does it have to also have a deps.edn? or would a project.clj work? i dont think so, but its been a while.

the former

sorry, could you clarify? i asked my question awkwardly. It must have a deps?

it must have either a deps.edn or a pom.xml

or neither

deps does not currently support project.clj as a manifest as there is no good way to canonically load it and find the deps without basically running all of lein

right, thanks alex.

because project.clj is evaluated, can be modified by plugins, etc