Clojurians Log v2
boot-dev 2017-12-19
suggestions for a SNAPSHOT version number with the Pomegranate change above? 🔺 2.8.0-SNAPSHOT 🔸 2.7.3-SNAPSHOT
^ can we get a consensus on how boot should handle symlinks?
Probably 2.8.0 is better, I even think we should get a 3 just to make clear that we bumped pomegranade
I see why we’d go straight for 3.0.0 but at the same time it’s not a breaking change really is it? I guess at some point we should come up with some more well-defined versioning scheme
You are probably right, mine is more like defensive programming I guess 😄
Well, defensive seems good. We just need something that we can consistently follow. If we decide fresh everytime that probably won’t be very consistent 😛
FWIW I don’t have any strong feelings about going straight to 3.0.0, if anyone else here thinks we should do that, make yourself heard 🙂
Agree totally with you first point, I feel that bumping the dep resolution is a strong motivator...but then let's agree of what it is and what not...I guess 😄
3.0.0 suggests some pretty major changes -- so I think 2.8.0 strikes the right balance.
@flyboarder I have never run into that, how to test it?
@richiardiandrea im no longer running into this issue, however if you place a symlink within a boot/tmpdir! and add-resource with that directory you should see the issue, basically the symlink was being turned into a corrupt file
but this might be resolved already
@alandipert hey, can you add me to the boot group on Clojars? 🙂