Intermittent outages at mirror.racket-lang.org yesterday and still
ongoing today. downloads.racket-lang.org changed this default, so I'm
doing same. Can change back later, if/as/when they do.
Also update the commented-out example of packages:
- No need to `cd`; can run `raco pkg install` in the repo dir.
- Add a step to check the package deps.
Namely, added test.sh to run through all the possible downloads and test for validity.
Added handler for TEST=1 in install-racket.sh.
Normalize urls as much as possible and to get minimal installs working
properly. This can probably be merged to master and drop the minimal
branch entirely.
I think there is still some cleanup that can happen. The various linux
flavors can probably be unified, if not parameterized.
This patch removes SCOPE_SNAPSHOT, as it seems to point to incredibly
stale content. RELEASE does too, but there is a note that it is only
valid during release phases.
Change install-racket.sh to:
- Use a RACKET_DIR env var saying where to install Racket. For backwards
compatibility, if undefined this defaults to /usr/racket.
- Don't use sudo unless installing to /usr*.
- Download nightly snapshot builds from Northwestern not Utah.
See https://github.com/travis-ci/travis-ci/issues/3012
- Fix the here string (which was slightly broken all along, although in
a way that had been harmless).
Change the example .travis.yml to:
- Split env into global and matrix sections.
- Specify RACKET_DIR as a global var.
- Specify the RACKET_VERSIONs as matrix vars.
- Set PATH from RACKET_DIR (because install-racket.sh can't do this --
it can't change the env for the .travis.yml).
History/background:
1. Originally, used curl with raw.github.com to get the latest version
of install-racket.sh.
2. But GitHub discourages using raw.github.com. So switched to using the
GitHub "releases" feature to make install-racket.sh available. But
that's a PITA: (a) Need to make each release, and furthermore (b)
there's no URL meaning "the latest version of the file to be
downloaded" for the .travis.yml scripts to use, so they tediously need
to be updated to fetch using the new URL for the new version.
3. OK, so now -- how about simply cloning the GitHub repo locally, and
using the travis-racket.sh from that (which of course will be the latest
version).
