[squeak-dev] Packaging conventions for Objectland - The Worlds of Squeak (was: Objectland - The Worlds of Squeak)

David T. Lewis lewis at mail.msen.com
Thu Oct 20 00:31:55 UTC 2022

I am a huge fan of Objectland, and I am also a big proponent of reloadable
packages. Reloadable means that I can completely remove a package from the
image, then add it back in, and everything still works.

With the recent addition of Objectand to trunk (yay!) I want to also note
that this seems like a great candidate for a reloadable package. After all,
we just loaded it, so we know that part works. All we need to do is make
sure we can unload it and then put it back in.

So this leads to a question - if we want this to be reloadable, then
what should be the package name? I am thinking that 'Objectland-Morphic'
would work well, and would be consistent with existing package names
such as 'ToolBuilder-Morphic'.

If this makes sense, then can we open a new package 'Objectland-Morphic'
and start moving these recent changes into that new package? The goal
would be to be able to remove 'Objectland-Morphic' completely from
any image, than load it again from the trunk repository with everything
still 100% working.


More information about the Squeak-dev mailing list