Pharo support for magma repositories

[Chris Muller]

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.

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.

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.

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.

 - Chris



On Sun, May 1, 2011 at 3:06 PM, Markus Fritsche
<fritsche.markus at googlemail.com> wrote:
> Hello,
>
> sure - I just wanted to push it away from my hard disc (scary, unsafe
> place for smalltalk code) to a repository.
>
> If Chris add me to one of the Magma repositories, I am happy to use
> that one for my commits.
>
> Regards,
> Markus
>
> 2011/5/1 Igor Stasenko <siguctua at gmail.com>:
>> Hi, Markus.
>>
>> I'm sorry, maybe i'm out of sync, but may i ask why you created a
>> separate repository for it?
>> I think it would be better to commit to magma repository (of course
>> you need to ask for access).
>> But keeping everything in single place is better.
>>
>> I think that changes are not too big for making a copy of  all
>> packages in separate repository.
>> If i remember correctly , Chris already had Magma-Pharo, and
>> Magma-Squeak specific installations,
>> which used to contain a fork-specific stuff.
>> If not, i think it worth to create them, in order to keep a shared
>> codebase in single place,
>> and only what is different in separate packages.
>>
>>
>> On 1 May 2011 16:56, Markus Fritsche <fritsche.markus at googlemail.com> wrote:
>>> Hello,
>>>
>>> I registered a project at squeaksource:
>>> http://www.squeaksource.com/MagmaPharoSupport.html
>>>
>>> In my pharo image ;-) (I will check loading in a clean pharo image in
>>> a bit) this enables using (local, server not yet tested) magma
>>> repositories with the Pharo version of Monticello. It also alters the
>>> cleanup-method of MagmaSession to be working with Pharo (PointerFinder
>>> vs. ProtoObject>>#pointersTo).
>>>
>>> If anyone wants to join the project, you're welcome.
>>>
>>> Pharo version:
>>> Pharo1.3a
>>> Latest update: #13177
>>>
>>> Magma:
>>> Ma client server cmm.217
>>> Ma base additions cmm.187
>>> Magma server cmm.425
>>>
>>>
>>> Kind regards,
>>> Markus Fritsche
>>> _______________________________________________
>>> Magma mailing list
>>> Magma at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/mailman/listinfo/magma
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>