[squeak-dev] Re: Updated trunk image (Squeak3.11-8472-alpha.zip)
Ken G. Brown
kbrown at mac.com
Sun Dec 13 22:04:08 UTC 2009
Note particularly the 'Unloading' section from:
More Installer and Sake/Packages documentation
<http://squeaktipsandtrickswatch.blogspot.com/2009/11/more-installer-and-sakepackages.html>
==============================================================
Sake/Packages usage:
Definitions Search Path
============================
Packages named: 'PackageName'.
Will obtain a package definition. Subclasses of Packages are searched using the order defined by #findPath which is specified by #priority.
e.g. Packages findPath => {PackagesSqueak310 . PackagesDev . PackagesAll . PackagesSeaside29}
Packages-#priority is used to sort classes like so:
The class with defns for a relevant version (listed in #relevantVersions) => 100
The class with defns for dev version (PackagesDev) => 400
The class with defns for all versions (PackagesAll) => 500
Additional package "universes" can define their own priority in order to specify where to appear in the #findPath.
PackagesSeaside29
PackagesGjaller
PackagesBeach
Usage:
========
verbose usage specifying run style.
(Packages named: 'Seaside') run. " or runQuietly, runStepping, runLogging"
#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.
default usage:
Packages load: 'Seaside'.
Packages latest: 'Seaside'. "as above, but use latest versions of everything"
Packages unload: 'Seaside'.
multiples:
Packages load: #('Seaside' 'Magma' 'Logging')
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' .
Packages unloadStepping: 'Seaside' .
Then the 'historical' unload scripts are used, as defined when the original load tasks were run.
If instead you perform:
(Packages current named: 'Seaside') beUnloading 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'.
Will unload whichever of the two are loaded.
=============================================================
Ken G. Brown
At 1:43 PM -0800 12/13/09, Andreas Raab apparently wrote:
>Edgar J. De Cleene wrote:
>>>I like it but we should have a community understanding what we'd like to
>>>see in the "standard" image. It may be similar to FunSqueak but it would
>>>be good if we'd have some discussions about the things we'd like to see
>>>in it.
>>
>>I send many mails for agree on some.
>>I want consensus, not doing my will
>>We want the bigger image with the all things which run without odd glues ?
>>Yes No
>>If the answer is yes
>>
>>Which one more ? Some in the image NOT should be ?
>
>I think a good starting point would be to take the latest trunk image list the packages in it, add those that you've got currently in FunSqueak and then come up with a prioritization along the lines of:
>
>1. Packages that should be in the core image
> (e.g., Kernel, Compiler, Collections)
>
>2. Packages that should be in the default image
> (e.g., MVC, Universes, Sound, Games etc)
>
>3. Packages that should be trivially loadable
> (e.g., Seaside, Aida)
>
>Once we have a structure like that we can talk a little more if there are other packages that really should be part of one of the layers and then be a bit more realistic about what's achievable ;-) and finally we should just execute on that structure by doing whatever is necessary to get the packages into their proper layer.
>
>Cheers,
> - Andreas
More information about the Squeak-dev
mailing list
|