<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple style='word-wrap: break-word; -khtml-nbsp-mode: space;-khtml-line-break: after-white-space'> <div class=Section1> I have a fix that, at least, works for my planet collection.  Jacob needs to look it over and make sure it doesn’t break anything else.  It also addresses Eli’s concern about not changing the info.ss language.  My info.ss file is back to the original with compile-subcollections being a list of list of strings:<o:p></o:p> <o:p> </o:p> (module info (lib "infotab.ss" "setup")<o:p></o:p>   (define name "PLT Scheme Science Collection")<o:p></o:p>   (define blurb<o:p></o:p>     (list "A collection of modules that provide functions for "<o:p></o:p>           "numerical computing."))<o:p></o:p>   (define categories '(scientific))<o:p></o:p>   (define doc.txt "doc.txt")<o:p></o:p>   (define primary-file "science-with-graphics.ss")<o:p></o:p>   (define version "2.0")<o:p></o:p>   (define compile-subcollections<o:p></o:p>     (list (list "special-functions")<o:p></o:p>           (list "random-distributions")))<o:p></o:p> )<o:p></o:p> <o:p> </o:p> The changes are limited to one routine (planet-cc->sub-cc) in the setup-unit.ss file in the setup collection.  The new definition (with replaced statements commented out and the replacement following it):<o:p></o:p> <o:p> </o:p>       ;; this is an awful hack<o:p></o:p>       (define (planet-cc->sub-cc cc subdir)<o:p></o:p>         (match-let ([(('planet owner pkg-file extra-path ...) maj min) (cc-shadowing-policy cc)])<o:p></o:p>           (planet->cc <o:p></o:p>            ;(build-path (cc-path cc) subdir)<o:p></o:p>            (apply build-path (cc-path cc) subdir)<o:p></o:p>            owner<o:p></o:p>            pkg-file<o:p></o:p>            ;(append extra-path (list (path->string subdir)))<o:p></o:p>            (append extra-path (list subdir))<o:p></o:p>            maj<o:p></o:p>            min)))<o:p></o:p> <o:p> </o:p> I guess I should suspect code that starts with such an ominous comment. J<o:p></o:p> <o:p> </o:p> With that change, the collection (and subcollections) correctly compiles when it is installed using ‘planet --file science.plt williams 2 0’.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: plt-scheme-bounces@list.cs.brown.edu [mailto:plt-scheme-bounces@list.cs.brown.edu] On Behalf Of Williams, M. Douglas Sent: Tuesday, December 27, 2005 3:08 PM To: plt-scheme Subject: RE: [plt-scheme] Problems and Questions converting to PLaneT<o:p></o:p> </div> <o:p> </o:p> Actually, I looked at the log file and now I have the following error message related to the compilation:<o:p></o:p> setup-plt: Warning: ...tings\williamsm\Application Data\PLT Scheme\planet\300\300\cache\williams\science.plt\2\0\info.ss:11:17: compile: unbound variable in module in: string->path<o:p></o:p> <o:p> </o:p> Using the string->path fixed one problem and seems to have caused another.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> <div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: plt-scheme-bounces@list.cs.brown.edu [mailto:plt-scheme-bounces@list.cs.brown.edu] On Behalf Of Williams, M. Douglas Sent: Tuesday, December 27, 2005 2:59 PM To: plt-scheme Subject: RE: [plt-scheme] Problems and Questions converting to PLaneT<o:p></o:p> </div> <o:p> </o:p> Jacob, thanks for the answers.<o:p></o:p> <o:p> </o:p> One more question based on your answers.<o:p></o:p> >Now I just need to know if there is a convenient way to compile it – i.e. something similar to compile-collection-zos when >something isn’t actually in the collection path.<o:p></o:p> >PLaneT for v300 automatically compiles .plt files when it installs them (this is in contrast to PLaneT for v20x).<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Shouldn’t it also them compile the package when it’s is installed using the command line?  It doesn’t in this case.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> </div> </div> </div> </body> </html>