The Racket repository
efc5a05049
Previously, if a dispatched build failed the files from the previous build would still get copied. This was an intentional feature, since only the compiled binaries of these builds are used, and usually these would work fine (with the zo files that were built on the main machine). Now, the build directory is deleted when starting, which means that any failure in a remote build means that the whole build will fail. This turns out to be better since when there are problems, the previous behavior could be very confusing. In addition, the racket setup itself rarely fails, so this won't make a difference. |
||
|---|---|---|
| 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-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.