Hello All,

The Sake/Packages unloading process should now be functional, though the 
recommended usage is slightly changed.

enjoy

Keith

-----------------
(from the class comment)

Sake/Packages usage:

Public API
============
"load package definition for your current version of Squeak"
(Packages current load: 'Seaside') run.  " or runQuietly, runStepping, 
runLogging"
(Packages currentBeta load: 'Seaside') run.

multiples:

(Packages current load: #('Seaside' 'Magma' 'Logging') ) run.

Run-variants
=========

#runStepping , - presents a confirm/debug dialog before each action.
#run                 - default.
#runQuietly     - auto-confirms any SakeConfirm dialogs.
#runLogging    - Writes any SakeStop warnings to self log.

Unloading
========
Unloading comes in two variants.

Each package task loaded by Sake/Packages is remembered in the 
'provided' list
If you perform:

    (Packages unload: 'Seaside') runStepping.

Then the 'historical' unload scripts are used, as defined when the 
original load tasks were run.

If instead you perform:

    (Packages current named: 'Seaside') unload runStepping.
 
Then the most recently defined unload script will be run.

Note: If packages such as "Magma server" and "Magma client" provides 
"Magma", then

    (Packages unload: 'Magma') run.

Will unload whichever of the two are loaded.

=====