Newbie questions again.

First, could somebody point me to a sample SAR file that might be 
considered by SqueakMap/SAR/Monticello gurus to be a canonical, good 
example of a SAR that:

1. Provides a preamble w/ dependencies loaded at user request.
2. Loads in a monticello file (instead of putting a 'mypackage.st' file 
in the SAR, puts a 'mypackage.mcz' file instead)

Also, if you build SAR files like the above, could you point me to the 
script or describe the methodology used to create it? Or just chime in 
w/ a tip on the best way? Can PackageInfo be told to use an MC file 
instead of using it's "native" ability to include a changeset for the 
package?

Also, I'd like to provide a good 'unload' procedure. My guess is that 
the best way to do this is to have Monticello unload it, and also to 
somewhere override the #removeFromSystem method to do all the 
unregistering and severing of pointers and dependencies. Is this the 
best way? It assumes MC is in the image, however -- perhaps MCInstaller, 
which seems to be headed for base image inclusion, could be beefed up to 
include an unloader too, so it's presence can be relied upon.

Would it be fair to say that SqueakMap, SAR, and Monticello have matured 
to the point that a thorough HOWTO for creating well behaved packages 
could now safely be written?