[plt-scheme] Problem with science.plt - any ideas?
I just downloaded V301 again and it loaded okay on this one, i.e. I didn't
get the build-path error.
This is a fresh Ubuntu Linux install I just did a few nights ago. And, the
source, etc for the science and simulation packages aren't on here. So it
is definitely downloading from PLaneT and installing ok on this machine.
Robby's comment on truncated downloads might be the answer.
I can send the .plt file by e-mail to anyone that is having problems.
Doug
-----Original Message-----
From: John Clements [mailto:clements at brinckerhoff.org]
Sent: Thu 3/2/2006 4:21 PM
To: Williams, M. Douglas
Cc: Kimberly Clark/Mike Messinides; plt-scheme at list.cs.brown.edu
Subject: Re: [plt-scheme] Problem with science.plt - any ideas?
On Mar 2, 2006, at 4:03 PM, Williams, M. Douglas wrote:
> I just downloaded it on a fresh install of v301.8 - I don't have
> V301 loaded
> on this machine. I have loaded it many times on various machines
> though.
> The only things I can think of is to erase the PLaneT directory
> where it is
> cached and I use Pretty Big as the language level (but I couldn't
> replicate
> your problem in other language levels either).
>
> Jacob, any ideas?
>
> Let me know if you have any luck.
>
> Doug
In 301, I get a setup error:
build-path: expects type <path, string, 'up, 'same> as 2nd argument,
given: ("special-functions"); other arguments were: #<path:/Users/
clements/Library/PLT Scheme/planet/300/301/cache/williams/science.plt/
2/1>
It would certainly appear that this problem stems from the format of
the info.ss file:
(module info (lib "infotab.ss" "setup")
(define name "PLT Scheme Science Collection")
(define blurb
(list "A collection of modules that provide functions for "
"numerical computing."))
(define categories '(scientific))
(define doc.txt "doc.txt")
(define primary-file "science-with-graphics.ss")
(define version "2.0")
(define compile-subcollections
(list (list "special-functions")
(list "random-distributions")))
)
In 301.8, I do not observe this problem. I conjecture that this
problem was fixed between 301 and 301.8, and I bet you can find out
more about it in the release notices.
John Clements