Fork me on GitHub
#clojure-nl
<
2019-02-12
>
skuro10:02:19

just found out that the new official clojure:lein-alpine docker image borked my build

skuro10:02:29

happy happy joy joy!

helios10:02:25

sad trombone

thomas10:02:53

don't you just love the smell of fresh containers in the morning?

lmergen10:02:57

that's nothing, recently the official openjdk docker images broke my build + that of many others

lmergen10:02:12

problem with the certificates so gpg did not work anymore

skuro10:02:06

who could have thought to see this happening in the era #semver, amirite?

borkdude10:02:55

calver is all the new rage

lmergen10:02:58

this is why i nowadays just pin every version of everything ever

lmergen10:02:07

calver ? calendar versioning ?

borkdude10:02:30

apparently. more and more clojure libs now use dates as their version numbers :-s

lmergen10:02:50

i have been seeing that also outside the clojure community

skuro10:02:31

that's aesthetically an improvement over the ocean of zero-dot versions in clojureland

skuro10:02:54

and it seems to me to convey the same amount of information

lmergen10:02:59

also, it doesn't pretend to convey any meaning since in clojure, outside of core, stuff breaks all the time

skuro10:02:09

my point exactly

borkdude10:02:13

just use git SHAs then, if there is no meaning.

lmergen10:02:14

also, semver was never as integrated in clojure / maven as it is in other languages (python, npm, where you can say foo >= 1.2)

lmergen10:02:38

@borkdude i would prefer something that is sortable by time though šŸ™‚

borkdude10:02:04

you still canā€™t rely on that with calver, since itā€™s still an ad hoc format

borkdude10:02:32

people should just try harder not to make breaking changes and if they do keep a changelog

borkdude10:02:34

that, or static types šŸ˜›

borkdude10:02:34

tbh I havenā€™t had much problems with breakage myself. most clojure libs I use I could upgrade without much trouble and had good documentation if they had breaking changes.

borkdude10:02:04

or Iā€™m deeply in denial, could also be

lmergen10:02:32

oh so it's just leiningen that doesn't support them ?

lmergen10:02:39

or am i an idiot ?

eval202010:02:05

Iā€™ve never seen them in the wild these ranges - and the resolution is somewhat less sophisticated than e.g. bundler if Iā€™m not mistaken (ie use the newest version)

gklijs18:02:12

It would be really awesome if some day there was a language/package tool that would guarantee the semantic versioning was right. So a guarantee minor and bug fix releases are 100% backwards compatible.

lmergen20:02:12

In Haskell they have ā€œstackageā€, which continuously tests all version combinations of all packages in the package repository, and provides you with the tools to ā€œpinā€ those versions.

lmergen20:02:03

When library authors break stuff, they are alerted and/or the community jumps on top of it to send PRs.

lmergen20:02:49

itā€™s opt-in for library authors to take part of it, but itā€™s a very good ā€œquality dealā€ that you know youā€™re dealing with a package author that wants to keep things stable.

lmergen20:02:59

I would love something like this for Clojure.