Some package systems like dpkg have "recommended packages". And if a package is dynamically needed, it should probably be checked for and fail gracefully with a meaningful message (saying that the package X should be installed).
Laurent On Tue, Nov 26, 2013 at 7:55 AM, Asumu Takikawa <as...@ccs.neu.edu> wrote: > 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? > > Cheers, > Asumu > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
