[racket-dev] Should `dynamic-require`d libraries be in package dependencies?

From: Asumu Takikawa (asumu at ccs.neu.edu)
Date: Tue Nov 26 01:55:08 EST 2013

Hi all,

Should dynamically required libraries induce a package dependency?

Take for example the "xrepl-lib" package. It currently depends on five
other packages, but I think two of them can be dropped and `raco setup`
won't complain.

On the other hand, XREPL may `dynamic-require` the macro stepper (one of
the dependencies that can be dropped). The same is true for DrRacket
(not listed as a dependency), but it doesn't make much sense to make the
XREPL package depend on DrRacket.

Is there a best practice for these kinds of cases yet?


Posted on the dev mailing list.