Gofer for Pharo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Gofer for Pharo

Mariano Martinez Peck
Hi Dale. Not sure which email address you are using, so I send this mail just in case. If you have a couple of minutes, could you take a look to http://code.google.com/p/pharo/issues/detail?id=4394 ?

thanks a lot in advance

--
Mariano
http://marianopeck.wordpress.com

Reply | Threaded
Open this post in threaded view
|

Re: Gofer for Pharo

Dale Henrichs
Mariano,

From my comment on the bug:

When gofer is deciding which package is newer:

  Gofer-Tests-MarcusDenker.129
  Gofer-Tests-StephaneDucasse.129

if first uses the version number, but for these two packages have the same version number (129), so gofer then goes to the author name and StephaneDucasse sorts after MarcusDenker so Gofer thinks that Gofer-Tests-StephaneDucasse.129 is the later package and Metacello (which has StephaneDucasse.129 specified in the config) goes ahead and loads the "newer version"...

A checkin using using a version number greater than 129 or an author starting with a letter greater than 'S' will "fix" the problem ...

Dale
----- Original Message -----
| From: "Mariano Martinez Peck" <[hidden email]>
| To: [hidden email]
| Sent: Friday, June 24, 2011 7:40:02 AM
| Subject: [Metacello] Gofer for Pharo
|
| Hi Dale. Not sure which email address you are using, so I send this
| mail just in case. If you have a couple of minutes, could you take a
| look to http://code.google.com/p/pharo/issues/detail?id=4394 ?
|
| thanks a lot in advance
|
| --
| Mariano
| http://marianopeck.wordpress.com
|
|