On Thu, Oct 4, 2018 at 9:34 AM Greg Hendershott <greghendersh...@gmail.com>

> > As to the dependency, there's no reason that people need to have
> handy/test-more (the testing framework I use for struct-plus-plus)
> installed in order to use the module.
> Would it help to put `handy` in `build-deps` instead of `deps`?

I could do that but it's only using handy/test-more and the build server is
going to have no idea what to do with test-more tests as opposed to
rackunit tests.

What I suppose I could do is make test-more run a rackunit test at the end
that verifies no tests failed so that the build server could do something
useful with it.  Will the build server care if there is STDOUT ouput from
the tests?

> > It's not clear to me how to use compile-omit-files in an info.rkt file.
> Are there examples I could look at?
> Near the bottom of https://docs.racket-lang.org/raco/setup-info.html
> where the compile-* options are mentioned, it links to the docs for
> `compile-collection-zos` where there's more explanation:

Doh.  I went through that page, but clearly not carefully enough.  Thanks
for the pointer.

> https://docs.racket-lang.org/raco/API_for_Raw_Compilation.html#%28def._%28%28lib._compiler%2Fcompiler..rkt%29._compile-collection-zos%29%29
> As for usage examples: I usually grep the Racket source and/or use
> GitHub search:
>   https://github.com/search?&type=Codel=Racket&q=compile-omit-paths
> [ In fact I should probably make that into a little Emacs command that
> prompts for the last query parameter then does `browse-url`. :) ]

You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to