Fork me on GitHub
#graalvm
<
2020-01-19
>
kulminaator20:01:39

does someone have a link to graalvm's native-image licensing explained for mere mortals ? 🙂

4
sogaiu20:01:03

may be you've seen it already, but fwiw: the first question at: https://www.graalvm.org/docs/faq/ touches a bit on native-image

kulminaator20:01:42

i know the question and "answer" is there

kulminaator20:01:56

but i'm really awful at lawyering

kulminaator20:01:08

that's why i was interested if someone has a human translation

kulminaator20:01:01

i see "graalvm community edition" , but in no sentence anywhere are they actually mentioning the licensing terms for native-image on top of the community edition. all the native-image license talk is related with the graalvm enterprise.

borkdude21:01:16

@kulminaator you can talk to the graalvm / native-image devs on the GraalVM slack as well

kulminaator21:01:03

i'm pretty sure somone has addressed the question already and has explained it

sogaiu21:01:19

fwiw, there are other issues that look like they might have some relevant bits: https://github.com/oracle/graal/issues?utf8=%E2%9C%93&amp;q=is%3Aissue+license+

sogaiu22:01:50

note the comment under the answer with score 71:

IANAL, but I am one of the creators of the Classpath Exception, and this is the right answer. The Exception was created to support AOT compiled embedded use cases where developers would be statically linking binaries (with gcj in our case). We needed something like the libgcc license, so I wrote the first version of the Classpath Exception based on that. It has since matured, but the spirit is the same.