It looks like there's not a way currently, although I think it would make sense to add one.
For file extensions generally, I think there should be an "info.rkt" field to add extensions that are recognized by all tools that apply to all collections. That's a larger project, but it's on my near-term list of things to do. At Fri, 21 Aug 2015 09:51:08 -0700, Matthew Butterick wrote: > The docs for `compile-collection-zos` [1] say that "all files with the > extension ".rkt", ".ss", or ".scm" in a collection are compiled" and that > within "info.rkt", one can specify paths to omit with `compile-omit-paths`. > > Is there way to go the opposite direction — specify *extra* files that should > be compiled — because they are bytecode-able, but don't use the three magic > extensions? > > > > > [1] > http://pkg-build.racket-lang.org/doc/raco/API_for_Raw_Compilation.html?q=compile > -collection-zos#%28def._%28%28lib._compiler%2Fcompiler..rkt%29._compile-collecti > on-zos%29%29 > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
