I understand. I thought it did more stuff, like remove necessary
development tools or executing processes, I don't know, but considering its
implementation it should affect only the image size, right?

Thanks,
Vitor

On Tue, Sep 13, 2016 at 8:30 AM, Marcus Denker <marcus.den...@inria.fr>
wrote:

>
> > On 13 Sep 2016, at 13:15, Vitor Medina Cruz <vitormc...@gmail.com>
> wrote:
> >
> > Humm, why not? When I load the configuration it loads several other
> packages, wouldn't that need a cleanup too? When I first see that I could
> cleanup an image my first thought was to put it in a production state with
> my code, then I would cleanup to leave it as lean as possible. Isn't that
> correct?
> >
> > If I should not clean after load my packages why provide the
> functionality? Why not provide clean images to be used in production so
> that people could download and load it's ready to production code?
> >
>
> No, the #cleanUpForProduction just unloads tests, examples and things like
> that… it only touches loaded code in the sense that it
> unloads all packages named -Tests and -Examples.
>
> But if the external package happens to be structured in a way that this is
> bad, it would brake.
>
> I never expected this to be run *after* more packages are loaded, just
> *before*.
>
> What it does right now it this (you can see that it could be simpler if
> our packages are better structured):
>
> cleanUpForProduction
>         "self new cleanUpForProduction"
>         "delete logo"
>         PolymorphSystemSettings showDesktopLogo: false.
>
>         self packagesForCleanUpInProduction do: [ :each | (MCPackage
> named: each) unload ].
>         self helpPackages do: [ :each | (MCPackage named: each) unload ].
>         self testPackages do: [ :each | (MCPackage named: each) unload ].
>         self examplePackages do: [ :each | (MCPackage named: each) unload
> ].
>         (MCPackage named: 'ScriptLoader40') unload.
>
>
>         (MCPackage named: 'MonticelloMocks') unload.
>         (MCPackage named: 'ToolsTest') unload.
>         (MCPackage named: 'Announcements-Tests-Core') unload.
>         (MCPackage named: 'AST-Tests-Core') unload.
>         (MCPackage named: 'AST-Interpreter-Test') unload.
>         (MCPackage named: 'Ring-Tests-Containers') unload.
>         (MCPackage named: 'Ring-Tests-Kernel') unload.
>         (MCPackage named: 'Ring-Tests-Monticello') unload.
>         (MCPackage named: 'Regex-Tests-Core') unload.
>         (MCPackage named: 'Refactoring-Tests-Changes') unload.
>         (MCPackage named: 'Refactoring-Tests-Core') unload.
>         (MCPackage named: 'Refactoring-Tests-Critics') unload.
>         (MCPackage named: 'Refactoring-Tests-Environment') unload.
>         (MCPackage named: 'FileSystem-Tests-Core') unload.
>         (MCPackage named: 'FileSystem-Tests-Disk') unload.
>         (MCPackage named: 'FileSystem-Tests-Memory') unload.
>
>         (MCPackage named: 'GT-Tests-Inspector') unload.
>         (MCPackage named: 'Glamour-Tests-Core') unload.
>         (MCPackage named: 'Glamour-Tests-Morphic') unload.
>         (MCPackage named: 'Glamour-Tests-Resources') unload.
>         (MCPackage named: 'Glamour-Tests-Rubric') unload.
>
>         (MCPackage named: 'Versionner-Core-Model') unload.
>         (MCPackage named: 'Versionner-Core-DependenciesModel') unload.
>         (MCPackage named: 'Versionner-Core-Announcements') unload.
>         (MCPackage named: 'Versionner-Core-Commands') unload.
>         (MCPackage named: 'Versionner-Spec-Browser') unload.
>         (MCPackage named: 'Versionner-Tests-Core-Commands') unload.
>         (MCPackage named: 'Versionner-Tests-Core-DependenciesModel')
> unload.
>         (MCPackage named: 'Versionner-Tests-Core-Model') unload.
>         (MCPackage named: 'Versionner-Tests-Resources') unload.
>
>         self cleanUpForRelease.
>
>
>         Marcus
>
>
>

Reply via email to