As a result, our own .travis.yml can focus on testing
install-racket.sh as of the current commit.
(I am still using test.sh and `for` loops. It's not immediately
obvious to me how to express that instead using a Travis job matrix --
or that doing so would be any clearer.)
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).
