Understanding #bleedingEdge

I have a configurationOf A that requires in its baseline another configurationOf B with version #bleedingEdge. Load configurationOf A with version #bleedingEdge itself it does not lead to packages of B being updated. With updated I mean that the configurationOf B has been loaded before. But for #bleedingEdge I would assume it should update, no?

Norbert

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Norbert,

I would also assume that the configurationB #bleedingEdge version to be loaded, but I would like to see the specifications of both projects to be sure that the load that you are doing would indeed trigger a configurationB load, since the load will depend upon the specs and the load expressions... There can always be a Metacello bug involved, so I'd like to examine your case in more detail.

Are the configurations publicly available? If not, if you can supply the baseline from configurationA and the load expression you are using, I should be able to understand what is going on...

BTW what platform are you running on? If you are on Pharo2.0 I am not in control of the code that is loaded there ... I am not sure that all of the Metacello tests pass in the version of Metacello that ships in Pharo2.0 ... Just recently Christophe and I got the Metacello Preview ported to Pharo2.0 and when we looked at porting Metacello 1.0-beta.31.1.7 (a recent Metacello release) there were too many tests failing to contemplate porting it to Pharo2.0. Also I have no way of shipping bugfixes (if indeed there is a bug here) to Pharo2.0...

Dale

----- Original Message -----
| From: "Norbert Hartl" <[hidden email]>
| To: [hidden email]
| Sent: Monday, July 29, 2013 4:26:19 AM
| Subject: [Metacello] Understanding #bleedingEdge
|
| I have a configurationOf A that requires in its baseline another
| configurationOf B with version #bleedingEdge. Load configurationOf A
| with version #bleedingEdge itself it does not lead to packages of B
| being updated. With updated I mean that the configurationOf B has
| been loaded before. But for #bleedingEdge I would assume it should
| update, no?
|
| Norbert
|
| --
| You received this message because you are subscribed to the Google
| Groups "Metacello" group.
| To unsubscribe from this group and stop receiving emails from it,
| send an email to [hidden email].
| For more options, visit https://groups.google.com/groups/opt_out.
|
|
|

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Dale,

while preparing this reply I probably found the same culprit as most of the time: me. I think I wasn't really loading what I thought I would do.

So, I'll have a look and come back to you if necessary. Thanks for now.

Norbert

Am 29.07.2013 um 19:21 schrieb Dale K. Henrichs <[hidden email]>:

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

No problemo ... if it isn't obvious, send the specs along and I will take a look ...

Dale

----- Original Message -----
| From: "Norbert Hartl" <[hidden email]>
| To: [hidden email]
| Sent: Monday, July 29, 2013 12:01:09 PM
| Subject: Re: [Metacello] Understanding #bleedingEdge
|
| Dale,
|
| while preparing this reply I probably found the same culprit as most
| of the time: me. I think I wasn't really loading what I thought I
| would do.
|
| So, I'll have a look and come back to you if necessary. Thanks for
| now.
|
| Norbert
|
| Am 29.07.2013 um 19:21 schrieb Dale K. Henrichs
| <[hidden email]>:
|
| > Norbert,
| >
| > I would also assume that the configurationB #bleedingEdge version
| > to be loaded, but I would like to see the specifications of both
| > projects to be sure that the load that you are doing would indeed
| > trigger a configurationB load, since the load will depend upon the
| > specs and the load expressions... There can always be a Metacello
| > bug involved, so I'd like to examine your case in more detail.
| >
| > Are the configurations publicly available? If not, if you can
| > supply the baseline from configurationA and the load expression
| > you are using, I should be able to understand what is going on...
| >
| > BTW what platform are you running on? If you are on Pharo2.0 I am
| > not in control of the code that is loaded there ... I am not sure
| > that all of the Metacello tests pass in the version of Metacello
| > that ships in Pharo2.0 ... Just recently Christophe and I got the
| > Metacello Preview ported to Pharo2.0 and when we looked at porting
| > Metacello 1.0-beta.31.1.7 (a recent Metacello release) there were
| > too many tests failing to contemplate porting it to Pharo2.0. Also
| > I have no way of shipping bugfixes (if indeed there is a bug here)
| > to Pharo2.0...
| >
| > Dale
| >
| > ----- Original Message -----
| > | From: "Norbert Hartl" <[hidden email]>
| > | To: [hidden email]
| > | Sent: Monday, July 29, 2013 4:26:19 AM
| > | Subject: [Metacello] Understanding #bleedingEdge
| > |
| > | I have a configurationOf A that requires in its baseline another
| > | configurationOf B with version #bleedingEdge. Load
| > | configurationOf A
| > | with version #bleedingEdge itself it does not lead to packages of
| > | B
| > | being updated. With updated I mean that the configurationOf B has
| > | been loaded before. But for #bleedingEdge I would assume it
| > | should
| > | update, no?
| > |
| > | Norbert
| > |
| > | --
| > | You received this message because you are subscribed to the
| > | Google
| > | Groups "Metacello" group.
| > | To unsubscribe from this group and stop receiving emails from it,
| > | send an email to [hidden email].
| > | For more options, visit https://groups.google.com/groups/opt_out.
| > |
| > |
| > |
| >
| > --
| > You received this message because you are subscribed to the Google
| > Groups "Metacello" group.
| > To unsubscribe from this group and stop receiving emails from it,
| > send an email to [hidden email].
| > For more options, visit https://groups.google.com/groups/opt_out.
| >
| >
|
| --
| You received this message because you are subscribed to the Google
| Groups "Metacello" group.
| To unsubscribe from this group and stop receiving emails from it,
| send an email to [hidden email].
| For more options, visit https://groups.google.com/groups/opt_out.
|
|
|

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.