[racket-dev] building docs, compile collects

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 <samth at ccs.neu.edu> wrote:
> On Mon, Oct 25, 2010 at 5:15 PM, Jon Rafkind <rafkind at cs.utah.edu> wrote:
>> On 10/25/2010 03:06 PM, Sam Tobin-Hochstadt wrote:
>>> On Mon, Oct 25, 2010 at 4:54 PM, Jon Rafkind <rafkind at cs.utah.edu> 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
> samth at ccs.neu.edu
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev
>