On Wed, Aug 29, 2018 at 6:29 AM Erich Rast <er...@snafu.de> wrote: > The reason why I want this to be a multi-collection package is that the > framework without anything gui-related is fairly small and should be > required by default as (require appy). The GUI-related extensions on > the other hand import and re-export a lot of additional modules - there > might even be a complete abstraction layer over Racket's GUI classes > later - and so I want them to be required explicitly as (require > appy/gui). >
You don't need a multi-collection package to do this. If your structure is: appy/ | |--info.rkt |--main.rkt |--gui.rkt |--… Then `(require appy)` will import "main.rkt" and `(require appy/gui)` will import "gui.rkt". On the other hand, if you want users to be able to *install* the non-GUI portions separately, a multi-collection package isn't enough: that's what leads to the profligration of foo + foo-lib + foo-test + foo-doc package families. -Philip > > That being said, everybody seems to discourage making multi-collection > packages everywhere I've looked. Are they just more complicated or are > there plans to deprecate them in the future? > > Best, > > Erich > > -- > 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. > -- 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.
