From daf965ac9c2855a9f40806ba651698fb8368bac4 Mon Sep 17 00:00:00 2001
From: Greg Hendershott <greghendershott@gmail.com>
Date: Mon, 10 Apr 2017 23:57:24 -0400
Subject: [PATCH] Update Racket versions

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.
---
 .travis.yml | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 5e0c3f0..3b33bc7 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -22,13 +22,15 @@ env:
     # versions.
     #
     # The RELEASE snapshot is only available during the release process.
-    - RACKET_VERSION=5.3.4
-    - RACKET_VERSION=5.3.5
-    - RACKET_VERSION=5.92
-    - RACKET_VERSION=6.0
     - RACKET_VERSION=6.1
     - RACKET_VERSION=6.1.1
     - RACKET_VERSION=6.2
+    - RACKET_VERSION=6.3
+    - RACKET_VERSION=6.4
+    - RACKET_VERSION=6.5
+    - RACKET_VERSION=6.6
+    - RACKET_VERSION=6.7
+    - RACKET_VERSION=6.8
     - RACKET_VERSION=HEAD
     - RACKET_VERSION=RELEASE
 
@@ -54,19 +56,16 @@ install:
 before_script:
 
 # Here supply steps such as raco make, raco test, etc.
-#
-# Tip: Use `raco pkg install --deps search-auto <pkg>` to install any
-# required packages without getting stuck on a confirmation prompt.
 script:
   - raco make main.rkt
   - raco test -x .
 
-# NOTE: If your repo is a Racket package with an info.rkt that
-# includes some `deps`, the following is more elegant:
+# OR: If your repo is a Racket package with an info.rkt that includes
+# some `deps`:
 #
 # script:
-# - cd ..   # Travis did a cd into the dir. Back up, for the next:
-# - raco pkg install --deps search-auto --link <pkg>
-# - raco test -x -p <pkg>
+# - raco pkg install --deps search-auto
+# - raco setup -D --check-pkg-deps <your-package-name>
+# - raco test -x -p <your-package-name>
 
 after_script: