On Fri, Jul 17, 2015 at 10:55 PM, Greg Hendershott < [email protected]> wrote:
> > Now another point of confusion, setup made a directory called > 'compiled' so > > I gather raco setup is compiling modules into the compiled directory. > Will > > raco setup do this in an incremental fashion. Say if I mod one module > then > > run raco setup, will it just compile the one? Or will all the modules in > > the collection by compiled again? > > `raco setup` compiles only as necessary. (The `compiled` dir has both > .zo and .dep files. The latter help determine "necessary".) > > > p.s. This discussion is useful for understanding how to do a project > with separate foo, foo-lib, and foo-doc packages, like in the Racket > distribution. But -- is that split valuable enough to be worth the > hassle, for most packages? > The thing I was doing wrong is racket install from a directory after each change, when instead, apparently, the files can be left local in the directory and just updated incrementally with racket setup. The setup instead of install flow will save time, and avoid the dependency problem I had due to the split up. I'm not familiar enough with this to speak to whether the split is useful. I just chose a similar complexity package install to emulate after looking in the distribution. It does seem like a natural partitioning, lib, docs, examples... -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAGxFmCOU%3DAwd-gjffXQR9CSbD85neQkmKV%3Dx04fy3CdVKGHXpQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
