On 2/12/13, Frank Shearar <frank.shearar at gmail.com> wrote:
> (One problem: Installer's marked as being unloadable, and it's
> probably one of the last packages we'd want to unload.

Yes, the Installer package was probably included to demonstrate that
it is indeed unloadable.

The
> ExternalPackage-Foo scripts I'm writing use Installer. But then, I
> could always have those scripts load Installer as a prerequisite.)
>

For what is the aim now. Unloading packages and building a release by
reloading them again on the integration server the package 'Installer'
should be excluded from the list.

Are there other candidates which should stay?

--Hannes


code snippet taken from SmalltalkImage>>unloadAllKnownPackages

"Go unloading"
	#(	'ReleaseBuilder'
                'ScriptLoader'
		'311Deprecated'
                '39Deprecated'
		'Universes'
                'SMLoader' 'SMBase'
                'Installer-Core'
		'VersionNumberTests' 'VersionNumber'
		'Services-Base'
                'PreferenceBrowser'
                'Nebraska'
		'ToolBuilder-MVC'
                'ST80'
		'CollectionsTests'
                'GraphicsTests'
                'KernelTests'
                'MorphicTests'
		'MultilingualTests'
                'NetworkTests'
                 'ToolsTests'
                 'TraitsTests'
		'SystemChangeNotification-Tests'
                'FlexibleVocabularies'
		'EToys'
                 'Protocols'
                'XML-Parser'
                'Tests'
                'SUnitGUI'
		'Help-Squeak' 'HelpSystem' 'SystemReporter'
	) do:
                 [:pkgName|
			(MCPackage named: pkgName) unload.
			MCMcmUpdater disableUpdatesOfPackage: pkgName.
			].