[Pharo-dev] what is the trick to load Gofer Configuration in an image without Gofer?

Stéphane Ducasse stephane.ducasse at inria.fr
Wed Oct 2 03:10:24 EDT 2013


tx pavel

I will look at Ring too. Because I want to see why it is not a nice layer. But I see because for packages there is probably a need to have it there.
On Oct 2, 2013, at 8:59 AM, Pavel Krivanek <pavel.krivanek at gmail.com> wrote:

> For the Pharo Kernel I firstly in one job download the latest versions
> of network packages and save it in a form of .st file. Then I load
> them to the shrinked image.
> 
> Network packages:
> #('Zinc-Resource-Meta-Core' 'Zinc-Character-Encoding-Core'
> 'Network-Kernel' 'Network-MIME' 'Network-UUID' 'Network-Url'
> 'Network-URI' 'Network-Protocols' 'Zinc-HTTP' 'Zinc-Patch-HTTPSocket'
> 'Settings-Network')
> 
> MC and Gofer packages:
> #(  'PackageInfo' 'System-FileRegistry' 'RPackage-Core'
> 'RPackage-SystemIntegration' 'Monticello' 'MonticelloConfigurations'
> 'Settings-Monticello' 'Ring-Monticello' 'Gofer-Core')
> 
> To get the source code of the package I use:
> ScriptLoader latestSource: packageName location:
> 'http://smalltalkhub.com/mc/Pharo/Pharo30/main'
> It uses Zinc and ZipArchive so we can modify the second stage that
> loads MC and Gofer to do it directly. But for network packages we have
> to use preexported source files.
> 
> -- Pavel
> 
> 2013/10/2 Stéphane Ducasse <stephane.ducasse at inria.fr>:
>> 
>> 
> 





More information about the Pharo-dev mailing list