Pharo support for magma repositories

[Markus Fritsche]

2011/5/2 Chris Muller <asqueaker at gmail.com>:
> Hi Markus, thanks for taking action to keep Magma going for Pharo.
> However, I want to be careful about creating new places where Magma
> code is kept; new Pharo people will see "Magma-Pharo-Support" and will
> go there to get Magma.  If there is a problem I am not prepared to
> support that because I have limited resources; so I will be forced to
> say, "see the official installation page:
> http://wiki.squeak.org/squeak/2657", which only involves the official
> Magma repository, not this new one.

This was a mistake by me; I was not aware that adding of dependencies
to a monticello package silently copies the packages between
repositories.


> Thank you again for your initiative, but let's please coordinate.
> First, regarding the change you made in MagmaSession class>>#cleanUp,
> I actually don't think that code is necessary anymore since we moved
> from BlockContexts to BlockClosures.  We definitely don't want to let
> that be a reason to branch Magma's packages.

Ok.

> All of the other changes appear to be things that will be taken care
> of when Pharo integrates the Monticello Repository refactor from
> Squeak.  Once that is done, we most likely (hopefully!) won't need a
> Magma-Pharo-Support project at all.

Once that is done, the mcz should be changed to be empty.

> Of course, there is always the possibility of needing something to
> bridge Squeak<->Pharo divergence in the future, and when that time
> comes, we should discuss the best approach here on the list.  Until
> then, please know from the wiki that there is a "Magma Inbox" project
> on SqueakSource which is World-writable.

So should I create a package there (maybe with another name)?

Regards,
 Markus