The Racket repository
![]() This is triggered by an environment variable that points at a file that is used to cache polling results. If the variable is not specified just use all mirror links as usual. This way, for random builds when people try things out there is no problem, while the nightly builds (and my manual builds when there are changes) do the right thing. The file holds information about the polls, and verifies that the download exists -- if not, the link is not shown. If it is, then it tries to get the size of the remote file (via HEAD or via FTP), and if it doesn't match our download information, then drop it too. If no size informaion is available, include it, but re-poll after a few days. Even if the size matches, a re-poll will be done after a month, so stale mirrors will not stick. |
||
---|---|---|
collects | ||
doc | ||
man/man1 | ||
src | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
README |
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-2011 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.