[racket] install-pkg

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Sun Jun 20 08:51:00 EDT 2010

On Sun, Jun 20, 2010 at 4:19 AM, Laurent <laurent.orseau at 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.

On Sun, Jun 20, 2010 at 4:55 AM, Laurent <laurent.orseau at gmail.com> wrote:
> I also used `remove-pkg', but it also seemed to recompile more than needed
> (although a lot less than install-pkg). This time I did not stop it.
> It removed the package, but then when I tried to re-execute the file where
> which holds my call to remove-pkg, I get the following error:
> procedure get-compiled-file-sha1: expects 1 argument, given 2:
> #<path:reader_rkt.zo> #<path:compiled\drracket\errortrace>

I've pushed a fix that likely fixes this bug.


Posted on the users mailing list.