I'm pretty sure that "racket-test" needs to be split up. (For the initial cut, I just put the whole "tests" collection there.)
I'm not sure about compiling tests for the purposes of dependency checking. It sounds ok, but I have a feeling that I'm forgetting some reason that we disabled compilation for tests. At Tue, 2 Jul 2013 12:20:57 -0400, Sam Tobin-Hochstadt wrote: > Currently, the `racket-test` package has very few declared > dependencies, but this is wrong. The checking in 'raco setup' doesn't > catch this because the files aren't compiled, but at a minimum it > depends on `unstable/debug` (currently a hidden part of > `typed-racket-lib`) and some portions of htdp that aren't declared. > > This brings up (at least) 3 questions > > - What is it ok for `racket-test` to depend on? I'd like this set to > be small, so we can test the core without needing to build everything. > - Should we compile the contents of `racket-test` so that we get > dependency checking? > - Should parts of `racket-test` be split up? > > I'd like to figure this out, but I don't have answers yet. > > Sam > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev _________________________ Racket Developers list: http://lists.racket-lang.org/dev