Yes.
On Apr 26, 2004, at 6:34 PM, Matt wrote:
> For list-related administrative tasks:
>http://list.cs.brown.edu/mailman/listinfo/plt-scheme>>> Typically, things go like this:
>> I develop a script that does something.
>> I realize it could be more general. I make it more general.
>> I realize that a touch more tweaking, and I have a small library to do
> some relatively specific (but useful to me) task or tasks.
>> I realize I could use it on another machine.
>> I want to make a PLT file, but then I wonder what
>> (pack dest name paths collections [filter encode? file-mode unpack-unit
> plt-relative? requires conflicts at-plt-home?])
>> the difference between "paths", "collections", and the rest of the
> optional arguments mean, practically speaking, when I want to bundle up
> arbitrary directory "Foo" as a PLT module, drop it on another machine
> (of
> some other architecture), and have my module *just work* (eg. install
> into
> a relative (eg. ".plt-scheme") directory, and get picked up in my
> current
> collections).
>> I must admit, an example or two in the docs (next rev around) would be
> wonderful. In particular, how to take the half-way library I've
> developed
> (whatever it may be) and *simply* move it from one machine to
> another---or, for that matter, from one major rev of PLT Scheme to
> another.
>> Surely I'm missing something simple.
>> Thanks,
> M
>> _______________________________________________________________________
> _
> Matt Jadud
>http://www.cs-ed.org/blogs/mjadud/> Canterbury Weather: High 59 F / 15 C, Low 46 F / 8 C, Sunny intervals