https://github.com/juxt/edge/issues/132 ran into this on the latest cli. I can't figure out how I repro'd it initially, but I cannot now. Bit confused. Putting it in the "record" in cae it comes up again.
@dominicm Were you testing against prerelease versions at any time recently? There were some glitches in the new git
implementation that could bork local ~/.gitlibs
in some situations. Several of us testing against those versions had to rm -rf
~/.gitlibs` to fix it.
(I think everyone who went from stable to stable, without testing any prerelease versions, was OK?)
@seancorfield nope, I went straight to 814.
It was possible to get this on the old stable, I think due to concurrent downloads (I never reproed it)
I believe it should be harder for that to occur in new impl
I'm sure you'll be glad when you find a stable repro :D
Just as an example: https://github.com/borkdude/antq/blob/bb.edn/bb.edn (ported from this Makefile: https://github.com/borkdude/antq/blob/bb.edn/Makefile)
I did try to make it happen in the new version and could not
This makefile is bad
Like, the whole deal about makefiles is it tracks dependencies between files and has tasks that generate files
This make file has a target named 'pom' that is used to generate the file pom.xml
Which has no dependencies (like maybe on deps.edn?)
Gross
This task dsl is gross too. To impose a restrictive dsl without getting anything out of it (like dependency tracking) is silly. If you aren't doing extra stuff (dependency tracking, staleness tracking, rebuilding, etc) the just use normal clojure functions
You want give some bit of functionality a name, and call it, we have defn for that
This isn't my makefile btw, I just scouted some makefiles in the wild, and what I mostly see is that people just use it as a way to quickly invoke it from the command line. It's clear that you don't see the value of this, that was already clear in our earlier conversation. Thanks for the feedback.
I do want to consider tracking, etc, like make does, it's done done yet