If I run 'racket -f quiet.rktl' in collects/tests/racket a bunch of collects will be pulled in (mzlib, scheme, racket, etc.). So I would need to do 'raco setup -D racket mzlib scheme', not to mention first figure out what collections are pulled in to begin with.
On 10/25/2010 03:57 PM, Robby Findler wrote: > Oh, yes. Just run "make install" and then "raco setup -D racket". > Write it down on a postit and stick it on your screen. :) Or make a > little script that does the whole git pull thing and onwards. > > Robby > > On Mon, Oct 25, 2010 at 4:22 PM, Sam Tobin-Hochstadt <[email protected]> > wrote: >> On Mon, Oct 25, 2010 at 5:15 PM, Jon Rafkind <[email protected]> wrote: >>> On 10/25/2010 03:06 PM, Sam Tobin-Hochstadt wrote: >>>> On Mon, Oct 25, 2010 at 4:54 PM, Jon Rafkind <[email protected]> wrote: >>>>> My motivation is to quickly test changes to core libraries (like >>>>> collects/racket) after doing a 'git pull --rebase'. >>>> Given that this is your motivation, why not just use: >>>> >>>> 'raco setup -D' >>>> >>>> which skips the documentation altogether? >>> The issue is building collects that I don't care about nor do the tests >>> exercise (like algol60, or all of drracket). In the event that there is >>> some subtle issue between my changes and a collect that I don't want to >>> build then DrDr will find it. >> Try 'raco setup racket' >> -- >> sam th >> [email protected] >> _________________________________________________ >> For list-related administrative tasks: >> http://lists.racket-lang.org/listinfo/dev >> _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
