Clojurians
#boot-dev
<
2017-12-19
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

martinklepsch11:12:20

suggestions for a SNAPSHOT version number with the Pomegranate change above? :small_red_triangle: 2.8.0-SNAPSHOT :small_orange_diamond: 2.7.3-SNAPSHOT

flyboarder18:12:50

^ can we get a consensus on how boot should handle symlinks?

richiardiandrea21:12:11

Probably 2.8.0 is better, I even think we should get a 3 just to make clear that we bumped pomegranade

richiardiandrea21:12:31

@flyboarder I have never run into that, how to test it?

flyboarder21:12:01

@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

flyboarder21:12:19

but this might be resolved already

martinklepsch22:12:16

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

richiardiandrea22:12:13

You are probably right, mine is more like defensive programming I guess :smile:

martinklepsch22:12:22

@alandipert hey, can you add me to the boot group on Clojars? :slightly_smiling_face:

martinklepsch22:12:13

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 :stuck_out_tongue:

martinklepsch22:12:48

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 :slightly_smiling_face:

richiardiandrea22:12:19

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 :smile: