We haven't done it before yet. The simplest way is to commit something to the core, but that's not good in the long run.
One thing that we could do is create a directory like meta/drdr/external of scripts that download something from the Internet and run it. We'll have to think of a good way to make it secure (such as having this script know the sha1 of the zip it is downloading.) Also, for parallelization purposes, it will be important for it not to require the use of "raco setup" to get started. Does that sound plausible for Whalesong? If so, I can work out a template for you. Jay On Mon, Oct 22, 2012 at 5:51 PM, Danny Yoo <d...@hashcollision.org> wrote: > During release testing for 5.3.1, I found that Whalesong broke in a > few ways. I'd like to detect the problem in a better way than what > I've been doing now. What's involved in getting into the DrDr > automatic build bot, and how would I get it to track Whalesong as I > continue to develop it? > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________ Racket Developers list: http://lists.racket-lang.org/dev
