The Racket repository
Go to file
Matthew Flatt 46fb91cfe4 update pre-built binary path for a win32 patch
Also, describe the patch in the Windows build notes.

This change increases access to symbol fonts, though not in a
completely consistent and portable way. See the closed problem
report for more information, as well as a 24-NOV-2012 post
on the Racket mailing list:
 http://lists.racket-lang.org/users/archive/2012-November/055141.html

Closes PR 13300
2012-11-28 05:39:46 -07:00
collects slideshow: fix import that changed the style of legacy libraries 2012-11-28 05:39:45 -07:00
doc make case' in r5rs' and r6rs' still use eqv?' 2012-11-26 19:49:36 -07:00
man/man1 Remove old packages 2012-07-13 15:43:59 -04:00
src update pre-built binary path for a win32 patch 2012-11-28 05:39:46 -07:00
.gitattributes Don't include git files in archives. 2010-05-12 01:46:05 -04:00
.gitignore Moved default location for compiled-root for easier tab-completion of "collects/". 2012-09-26 14:50:31 -04:00
.mailmap Another email for Matthew. 2012-11-07 11:22:19 -05:00
README 2011 -> 2012 2011-12-31 15:16:59 -05:00

The Racket programming language
===============================

Important executables:

* DrRacket: Racket's integrated development environment (start here!).

* Racket: the main command-line entry point for running racket programs
  and scripts.

* GRacket: the GUI-mode Racket executable.

* raco: Racket's command-line toolset.


More Information
----------------

Racket comes with extensive documentation: use DrRacket's `Help' menu,
or run `raco docs'.  Also, visit us at http://racket-lang.org/ for more
Racket resources.

Instructions for building Racket from source are in src/README.


License
-------

Racket
Copyright (c) 2010-2012 PLT Scheme Inc.

Racket is distributed under the GNU Lesser General Public License
(LGPL).  This means that you can link Racket into proprietary
applications, provided you follow the rules stated in the LGPL.  You can
also modify Racket; if you distribute a modified version, you must
distribute it under the terms of the LGPL, which in particular means
that you must release the source code for the modified software.  See
doc/release-notes/COPYING.txt for more information.