I figured out how to get the installation directory by default, using --at-plt

So installation from file works fine now.

Putting the .plt on one of my webservers and installing from URL still gives 
the format error.

-- Éric


On Nov 15, 2011, at 11:17 AM, Robby Findler wrote:

> Planet creates .plt files that are meant to be installed via the
> planet command-line tool or via (require (planet ...)) after they've
> been uploaded to planet.
> 
> If you want to install them via DrRacket (is that what you're doing?)
> then you probably want to use 'raco pack' to create them.
> 
> Robby
> 
> On Tue, Nov 15, 2011 at 8:11 AM, Eric Tanter <etan...@dcc.uchile.cl> wrote:
>> Hi,
>> 
>> I am creating a small plugin for the first time.
>> 
>> I create the .plt file using: raco planet create mydir/
>> 
>> While "it works", I get some problems with installation:
>> 
>> - if I install the .plt "from file", the install works but for some reason I 
>> have to manually specify the target directory (a window pops up 
>> systematically, asking for the directory). This does not happen with other 
>> .plt files I install manually. (I'm on mac os, these .plt get installed in 
>> ~/Library/Racket/5.2/collects)
>> 
>> - I put the .plt file on a web server and tried to install .plt "from web". 
>> In that case I get an error:
>> gnu-unzip: bad header
>> 
>>  === context ===
>> /Applications/@Sync/Racket/collects/mzlib/inflate.rkt:857:2: do-gunzip
>> 
>> not an unpackable distribution archive
>> 
>>  === context ===
>> /Applications/@Sync/Racket/collects/setup/unpack.rkt:271:7
>> 
>> 
>> Is there something special to specify so that the package can be installed 
>> from web, and automatically in the local collects?
>> 
>> Thanks in advance!
>> 
>> -- Éric
>> 
>> _________________________________________________
>>  For list-related administrative tasks:
>>  http://lists.racket-lang.org/listinfo/users
>> 
> 


_________________________________________________
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/users

Reply via email to