22 Sep
2010
22 Sep
'10
4:31 p.m.
On Wed, Sep 22, 2010 at 3:34 PM, Simon Denier <Simon.Denier(a)inria.fr> wrote:
On 22 sept. 2010, at 15:20, Mariano Martinez Peck wrote:
On Mon, Sep 20, 2010 at 4:50 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote;wrote:
The only reason I found is what Stef said...if you want to help Pharo,
report issues and fix them, then this is useful.
We have to make sure that Pharo 1.2 is working
well. Yesterday, I couldn't
inspect a value from the debugger because of an error raised with some
mapping with closure. This is annoying.
But 1.2 CAN be annoying. And it CAN be even unstable. That's why its label
says "unstable".
You cannot make progress without breaking things.
I see you guys (Moose) doing a lot of effort for Pharo 1.2....why you need
so much that ? Maybe you should wait a little until Pharo 1.2 gets code
freeze and releases a first beta or RC.
As far as I'm concerned, I didn't even try to load Moose in Pharo 1.2 :)
I just let other people debug the process for now...
That's why I was asking whether 1.2 fixes could break a 1.1 image. If yes,
it's already done and we can move on while retaining a stable dev
environment.
Actually, we had another motivation to load Moose in 1.2 which was building
Hudson reports, but we will probably try a different way now, using
Metacello and Monticello importer.
However, I do not think it is useful for a Hudson report. What is the sense
of reporting if Moose breaks on PharoCore 1.2 if PharoCore1.2 can be broken
even itself ?.
Again, from my point of view, if you DO spend time trying to use Moose in
Pharo 1.2, then create issues in Pharo and try to fix them. Otherwise, just
wait until it is stable.
Cheers
Mariano
Alexandre
On 20 Sep 2010, at 10:43, Laval Jannik wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I just tried to load Moose on pharo1.2
I only do this script (loading OB is not needed I think):
=====
Gofer new
squeaksource: 'rb';
package: 'AST-Core';
package: 'Refactoring-Core';
package: 'Refactoring-Critics';
package: 'Refactoring-Environment';
package: 'Refactoring-Spelling';
package: 'Refactoring-Changes';
load.
Gofer new
squeaksource: 'shout';
version: 'Shout-cyrille_delaunay.87';
package: 'ShoutWorkspace.1';
package: 'ShoutTests';
load.
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfOmniBrowser';
load.
((Smalltalk at: #ConfigurationOfOmniBrowser) project version: '1.1.5')
load.
Gofer new
squeaksource: 'Moose';
package: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
=====
With Cyrille, we fix a part of error tests. Now, I'm not sure that it
can work
on Pharo1.1.
So we do not save our work on moose repository.
What do we do for next steps ?
Do we change our Pharo system and go to 1.2 or working on 1.1 ?
Cheers,
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev