suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revise license page with the clarification text that was sent on the list.

Browse Source 
(Slightly revised.)
This commit is contained in:
Eli Barzilay 2012-05-02 03:12:27 -04:00
parent ed2b579e3c
commit 2fa345ef9e
1 changed files with 36 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
collects/meta/web/download/download-pages.rkt
View File

@ -110,15 +110,44 @@
(define license (define license
@page[#:title "Software License" #:part-of 'download]{ @page[#:title "Software License" #:part-of 'download]{
@p{Racket is distributed under the @p*{
@~ Racket is distributed under the
@a[href: "http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html#SEC1"]{ @a[href: "http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html#SEC1"]{
GNU Lesser General Public License (LGPL)}. GNU Lesser General Public License (LGPL)}.
This means that you can link parts of Racket (such as racket or gracket) @~ Our primary goal is to help as many people as possible use and
into proprietary applications, provided that you follow the specific contribute to Racket. We encourage anyone to develop any kind of
rules stated in the LGPL. You can also modify Racket software; if you software, with any kind of license, using Racket.
distribute a modified version, you must distribute it under the terms of @~ We have chosen the LGPL as the license for Racket, which makes it
the LGPL, which in particular means that you must release the source possible for for people to create software with Racket, and to allow us
code for the modified Racket software.}}) to build on existing libraries that use the LGPL, such as the Lightning
assembler and the GMP math library. The basic requirement of the LGPL
is that you make your changes to Racket available, and that you let
other people use your software with new versions of Racket.
@~ Since the LGPL license that Racket uses was originally designed for C
programs, parts of it require some interpretation to apply to Racket in
detail. The following is how the Racket maintainers interpret the
license.
@~ @ul*{
@~ First, if you distribute your Racket application in source form or as
compiled bytecode files, the Racket license does not restrict you at
all.
@~ Second, if you distribute your Racket application as compiled binary
generated by @tt{raco exe}, there are no requirements placed on the
licensing of your software. However, the LGPL requires that you make
it possible to re-link your software with modified versions of
Racket. This means, basically, that you need to provide the compiled
bytecode files used to produce the compiled binary, if requested by
someone who got your software from you. Note that this does @em{not}
mean that your software has to be made open source, nor do you have
to give the source code to anyone, nor do you have to make the
compiled bytecode files available to the public or let other people
redistribute them. Furthermore, this is not revealing any more of
your source code than the @tt{raco exe} format, since the bytecode is
embedded in an extractable way in the resulting executable.}
@~ We are, of course, not lawyers, and this should not be taken as legal
advice. However, we wanted to make it clear that Racket is an
appropriate building block for all kinds of software, and to clarify how
we view the license of Racket.}})
(define downloader-script (define downloader-script
@script/inline[type: 'text/javascript]{@|| @script/inline[type: 'text/javascript]{@||