Completing Racket's relicensing effort

Re:Completing Racket's relicensing effort by wtetzner on Monday November 18, 2019 @12:59PM (#21566470)

First, it is unclear how to apply the LGPL’s statement about dynamic linking to a language like Racket, where macro expansion can copy code from libraries to applications, and where applications are typically bundled with the Racket runtime and libraries. Second, some organizations unfortunately are unwilling to use software licensed under any variant of the GPL.

I wonder if this simplifies the Racket-on-Chez effort in any way as well.

[ Parent | on HN ]

Re:Completing Racket's relicensing effort by samth on Monday November 18, 2019 @05:24PM (#21568796)

Racket CS works similarly to traditional Racket in this respect -- compiled libraries still contain the results of macro-expansion and inlining from their dependencies, and generated executables still bundle everything together in a way that's not easy to re-link.

It's more the other direction that's a benefit -- traditional Racket makes fundamental use of several pieces of LGPL software, such as GNU Lightning and libgmp, but Racket CS does not use them and Chez Scheme is Apache-licensed.

[ Parent | on HN ]