I was just playing around with making a zip-based Squeak distribution 
format that could be used for multi-CS packages.

The enclosed change sets are able to store a (somewhat) 
self-installing archive to a zip file.

Actually, all they do right now is to execute the 'install/preamble' 
and 'install/postscript' members.

What I need help with is this:

I'd like (I think) to allow the preamble to (for instance) prompt for 
installation choices, etc. so that different CSs might be installed.

Likewise, the postscript may want to install other things.

For backwards compatibility, the entire logic has to live in the 
self-extracting stub at the front of the zip.

The problem is that the preamble and postscript code won't know what 
zip file is being installed, so they can't do anything intelligent.

I'd like either the zip stream, or the zip itself (better) to be 
available to this code, but that's hard to do, because there is no 
context for the compilation of the various chunks.

I'd thought about using a global (the easy way out), but that wasn't 
too appealing.

Another problem is that the self-extracting stub methods are logged 
and added to the current CS. I'd like the (re-re-re-) definition of 
the methods in the stub not to be logged.

Ideas?
-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ZipDistroLoader-nk.14.cs
Type: text/x-squeak-changeset
Size: 2237 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20021021/87ec6b75/ZipDistroLoader-nk.14.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ZipDistro-nk.6.cs
Type: text/x-squeak-changeset
Size: 4863 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20021021/87ec6b75/ZipDistro-nk.6.bin