Hi,
(I am copying the metacello mailing list here because I think we could join the efforts by dealing with Moose as a case study)
Stef, I did not see the reply of Dale. Where was it?
In any case, let's join our efforts. Who is willing to spend some focus time around this: - Johan said he would, but it is unclear when - Alex? - anyone else?
Doru
On 1 Jun 2011, at 07:32, Stéphane Ducasse wrote:
thanks
I think that this is really important to address that if the build does not work then why the rest is of importance since we cannot rollback. So please have a look. Moose is really important and also we should learn for the complete pharo system. Dale replied.
Stef
On May 31, 2011, at 10:53 PM, Tudor Girba wrote:
Hi,
The problem is that we need a script that given:
- a baseline (default in our case), and
- the packages from the current image
versions the current configuration and all the nested configurations. This does not seem to work properly because we have such a deep nesting of configurations. At this point, I would even be satisfied with having a specific configuration that lists all packages by flattening the nested configurations.
Cheers, Doru
On 31 May 2011, at 22:45, Stéphane Ducasse wrote:
Hi guys
I think that having a metacello configuration that is working for moose is key. So what are the problems?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not how it is, it is how we see it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving should be focused on describing the problem in a way that makes the solution obvious."