I'm using Travis CI for a number of my projects, to test them against recent Racket releases.
Sam had a great suggestion: Add 5.90.x to the build matrix. [1] I could update my .travis.yml to use e.g. http://www.cs.utah.edu/plt/snapshots/current/installers/racket-5.90.0.9-x86_64-linux-precise.sh That would work great...for awhile. But what happens if the version rolls to 5.90.0.10? I'd be fetching the old, wrong thing until someone noticed. Instead: Is there some "abstract" URL meaning (a) the latest version (b) of a platform like x86_64-linux-precise? For example instead of ... current/installers/racket-5.90.0.9-x86_64-linux-precise.sh it would be (say) ... current/installers/latest/x86_64-linux-precise.sh Note that I don't care what the actual filename ends up being. So this abstract URL could be a 302 Found redirect where the Location response header is whatever the specific version happens to be, just like the status quo. (I suppose anyone, even I, could set up such a redirect server. The problem would be coordinating it with the HEAD version bumps, and manually updating the redirect at the same time the version bumps. So same problem, just whacka-moled elsewhere.) [1]: https://github.com/greghendershott/frog/issues/56 ____________________ Racket Users list: http://lists.racket-lang.org/users
