> Now, I understand we could build images without development tools, but for
> that there is some work needed (not only from the pharo side but also from
> the developer's point of view).
> In the file server you can download latest minimal images both 32 and 64
> bits (http://files.pharo.org/image/70/):
> - Pharo-metacello-7.0.0-alpha.build.654.sha.494bbfc.arch.32bit.zip
> 10:314.4 MB
> - Pharo-metacello-7.0.0-alpha.build.654.sha.494bbfc.arch.64bit.zip
> 10:314.5 MB
> Those are ~4.5M zip files containing 10MB images and 9MB changes files.
> Probably that is small enough for you. We can do better but each line of
> code we remove is indeed a lot of work.
> Those images have the following packages installed only:
> - Language Kernel + Traits + Class builder + Slots
> - RPackage
> - FFI Kernel
> - Opal Compiler + AST + Chunk files reader writers
> - Announcements
> - Collections
> - Colors
> - Files
> - Others (Hermes, Jobs, Transcript, System packages, UIManager...)
> - Zinc Character encoders and Buffered streams
> - Network
> - Monticello
> - Metacello + Filetree
> For a more detailed list, you can browse BaselineOfPharoBootstrap.
> If you want an image that requires packages that are not there (like
> morphic), you should install them on top and specify those as dependencies
> of your project. That is what we do with the Pharo IDE. Take a look at
> BaselineOfIDE. Again, this could be enhanced and we will greatfully accept
> any contribution, or discuss on skype about the details or help people to
> get into this.
I love it. It opens so many doors.
4.4 mb for such a system is cool.
I'm eager to see what we will do with carolina.