![]() When the desired reference is not an advertised commit, then try pulling just a few commits --- at depth 8, 16, and 32 -- from the "master" branch to check whether the commit can be found that way. If not, fall back to the exhaustive search that requires a full download. This should help with the common case that a package reference into the Racket repo is a few commits behind the current master branch (because the package server hasn't scanned the repo recently enough). It's much faster to disover that the commit is within the first 32, which is almost always is, than to download the entire repository. |
||
---|---|---|
.github/ISSUE_TEMPLATE_DRAFT | ||
pkgs | ||
racket | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
appveyor.yml | ||
azure-pipelines.yml | ||
INSTALL.txt | ||
Makefile | ||
README.md |
This is the source code for the core of Racket. See "INSTALL.txt" for full information on building Racket.
To build the full Racket distribution from this repository, run make
in the top-level directory. To build minimal Racket, run make base
.
The rest of the Racket distribution source code is in other repositories, mostly under the Racket GitHub organization.
Contribute to Racket by submitting a pull request, joining the development mailing list, or visiting the IRC channel.
License
Racket is distributed under the GNU Lesser General Public License (LGPL). This implies that you may 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 states that you must release the source code for the modified software.
See racket/src/COPYING_LESSER.txt for more information.