Hi guys
I think that having a metacello configuration that is working for moose is key. So what are the problems?
Stef
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."
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
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."
On Jun 1, 2011, at 11:40 AM, Tudor Girba wrote:
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?
on the bug entry of alex.
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I think I should be able to look at this again somewhere next week.
On 01 Jun 2011, at 05:40, Tudor Girba wrote:
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Even if I already spent a lot of time on this, I am willing to pursue the effort. We could meet in a couple of weeks in Bern about this. But best is to have Dale around. Dale, will you be at esug?
Alexandre
On 1 Jun 2011, at 05:40, Tudor Girba wrote:
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I will try to allocate some time on it. even if my time is #$%^&*( short in this moment.
Stef
On Jun 1, 2011, at 4:01 PM, Alexandre Bergel wrote:
Even if I already spent a lot of time on this, I am willing to pursue the effort. We could meet in a couple of weeks in Bern about this. But best is to have Dale around. Dale, will you be at esug?
Alexandre
On 1 Jun 2011, at 05:40, Tudor Girba wrote:
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Alexandre,
I will be at ESUG, so that would be the best time to hash out the issues and come up with some real solutions...
Dale
----- Original Message -----
Even if I already spent a lot of time on this, I am willing to pursue the effort. We could meet in a couple of weeks in Bern about this. But best is to have Dale around. Dale, will you be at esug?
Alexandre
On 1 Jun 2011, at 05:40, Tudor Girba wrote:
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Super!!
Alexandre
On 1 Jun 2011, at 12:05, Dale Henrichs wrote:
Alexandre,
I will be at ESUG, so that would be the best time to hash out the issues and come up with some real solutions...
Dale
----- Original Message -----
Even if I already spent a lot of time on this, I am willing to pursue the effort. We could meet in a couple of weeks in Bern about this. But best is to have Dale around. Dale, will you be at esug?
Alexandre
On 1 Jun 2011, at 05:40, Tudor Girba wrote:
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."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Indeed. Last time I tried there was a bug in Metacello. I reported it, but I was full with other things: http://code.google.com/p/metacello/issues/detail?id=107
Alexandre
On 31 May 2011, at 16: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
Does it have to be a metacello configuration or any other means to do it automatically? I have been looking into the issue, trying to find a way to get a list of packages to load and in what order. If we have this, then a gofer script is enough. I am currenlty blocked at defining the load order of packages. Doru gave me some hints but I have not been able to look into it further (yet).
On 31 May 2011, at 16: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
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
-
Alexandre Bergel -
Dale Henrichs -
Johan Fabry -
Stéphane Ducasse -
Tudor Girba