<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Dec 27, 2005, at 3:13 PM, Williams, M. Douglas wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"> <DIV class="Section1"><P class="MsoNormal"><FONT size="2" color="navy" face="Arial"><SPAN style="font-size: 10.0pt;font-family:Arial;color:navy">I got it to work by changing the compile-subcollections in my info.ss file to a list of list of paths. The info.ss file is now: [...]</SPAN></FONT></P></DIV></BLOCKQUOTE>Yes, this makes sense. I'll look into fixing planet to be tolerant of strings there for future releases; thanks for tracking the source of the problem down.<BLOCKQUOTE type="cite"><DIV class="Section1"><P class="MsoNormal"><FONT size="2" color="navy" face="Arial"><SPAN style="font-size: 10.0pt;font-family:Arial;color:navy">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></SPAN></FONT></P><P class="MsoNormal"><FONT size="2" color="navy" face="Arial"><SPAN style="font-size: 10.0pt;font-family:Arial;color:navy"><O:P><BR></O:P></SPAN></FONT></P></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>PLaneT for v300 automatically compiles .plt files when it installs them (this is in contrast to PLaneT for v20x).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Now to respond to your earlier questions:</DIV><BLOCKQUOTE type="cite"><DIV class="Section1"><DIV style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><P class="MsoNormal"><FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial">In any case, I should be able to build the .plt file for distribution with PLaneT. I used make-planet-archive to create a plt file. This seems to work okay. (I assume that ‘planet --create-archive …’ would have done the same thing.)</SPAN></FONT></P></DIV></DIV></BLOCKQUOTE>Yes it would.<FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial"><O:P> </O:P></SPAN></FONT><BLOCKQUOTE type="cite"><DIV class="Section1"><DIV style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><P class="MsoNormal"><FONT class="Apple-style-span" face="Arial" size="4"><SPAN class="Apple-style-span" style="font-size: 13.3333px;"></SPAN></FONT></P><P class="MsoNormal"><FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial">Note that I cannot remove the package at this point. In particular, ‘planet --remove williams science.plt 2 0’ gives the following: [...]</SPAN></FONT></P></DIV></DIV></BLOCKQUOTE><DIV>Yuck, very bad error handling in that case. I'll fix it for future releases.<FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial"><O:P> </O:P></SPAN></FONT><FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial"><O:P> </O:P></SPAN></FONT></DIV><BLOCKQUOTE type="cite"><DIV class="Section1"><DIV style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><P class="MsoNormal"><FONT size="2" face="Arial"><SPAN style="font-size:10.0pt; font-family:Arial">Just out of curiosity, why is the order of the arguments to the --file option different from the others with similar arguments (-- install, --download, and --remove)?</SPAN></FONT></P></DIV></DIV></BLOCKQUOTE><DIV>I had what I thought was a good reason at the time, but I think I may no longer be persuaded by it -- it was to remind people that the file installer thing interprets version numbers in a different way than the others do; if you specify a particular user, package, and version with --download, say, it fetches whatever the planet require form would fetch and then installs it; on the other hand, --file installs exactly what you specify. But I don't think my ordering choice has yet actually suggested that to anybody, so it might be better to change the order so it's consistent.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-jacob</DIV></DIV></BODY></HTML>