On Wednesday, August 28, 2019 at 11:45:10 PM UTC+8, Joel Dueck wrote:
> On Wednesday, August 28, 2019 at 12:10:56 AM UTC-5, Alex Harsanyi wrote:
>> I am curious to know how you plan to comply with section 4.d of the LGPL, 
>> which states that the users of your application must be able to replace the 
>> LGPL "library" with a modified version of their own -- this means all the 
>> racket packages that you use in your application (even the ones shipped 
>> with Racket):
> Excellent question. I don’t intend to comply with the LGPL.
I was really hoping that you actually had a solution to the problem I

The LGPL clarification on https://download.racket-lang.org/license.html 
that we need to be able to re-link the software with modified versions of
Racket.  I am not sure how to achieve that, so here are my technical
questions, directed to anyone on this list who can answer them:

0) To simplify things, the same Racket version and OS can be used for both
   "raco make" to produce the bytecode files as well as the "raco exe" part 
   "link" the executable.

1) Given a set of ZO files compiled using "raco make", is it possible to
   create an executable from these ZO files using "raco exe", or a call to
   `create-embedded-executable`, without having access to the source files
   themselves?  If it is possible, how?

2) Is it possible to distribute a Racket package as ZO files only and 
   be able to use it from Racket? If it is possible, how?


You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to