On Sun, Jun 20, 2010 at 18:25, Robby Findler <ro...@eecs.northwestern.edu>wrote:
> On Sun, Jun 20, 2010 at 7:51 AM, Robby Findler > <ro...@eecs.northwestern.edu> wrote: > > On Sun, Jun 20, 2010 at 4:19 AM, Laurent <laurent.ors...@gmail.com> > wrote: > >> That worked, but there is one annoying thing: it recompiled *all* the > >> dependencies, including the whole Racket... > >> Is there a way to avoid this with this function? > > > > This is a bad interaction between drracket's automatic compilation > > setup and the planet tools. In general, these planet functions expect > > to be called in a fairly clean environment and, when they are called > > via the planet command-line tool or when they are called by a > > `(require (planet ...))', they do get that clean environment, but when > > they are called directly here, they don't. > > > > I'm not really sure if this is fixable, but I have not looked > > carefully at it yet. (I will at least try to document the restriction > > if I cannot lift it.) > > > > The simplest thing, for now, is to just make sure you call these from, > > say, a racket command-line script. > > I've adjusted planet a little bit so that now this works like you'd expect. > > But please let me know if you see other problems with planet now > compiling too much or too little in other situations.... > Thanks for the replies, Robby. Btw, is http://pre.racket-lang.org/installers/ really pointing to the right thing? I don't see new nightly builds, but maybe there isn't one yet.
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
