On Sun, Jan 10, 2010 at 9:10 PM, <csrabak@bol.com.br> wrote:
Em 10/01/2010 17:46, Mariano Martinez Peck <marianopeck@gmail.com> escreveu:
On Sun, Jan 10, 2010 at 8:37 PM, <csrabak@bol.com.br> wrote: Em 10/01/2010 13:04, Mariano Martinez Peck <marianopeck@gmail.com> escreveu:
PharoCore1.0rc1 Latest update: #10505
OK.
And if I am in Pharo I would see Pharo1.0-10505-rc1dev10.01.1 Isn't this ^^^^^ completely redundant with:
PharoCore1.0rc1 Latest update: #10505 <<<<<<<<<--- this?
the problem is what I have already said. If the user did a system update, the core will be higher that the dev image, and not the same.
I'm not so sure if I undertand this in full, so I'll test my understanding:
Do your assertion above means that an hypothetical:
Pharo1.0-10505-rc1dev10.01.1 that after some updates ends up reponding in System->About this:
Pharo1.0-10505-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10510
You say that it would be *different* than a brand new downloaded:
Pharo1.0-10510-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10510
Is it?
Exactly. Maybe is just a little detail. I don't know.
Maybe we can just don't care about this case or disable the system update in dev as we are discussing in another thread.
As an after thought after seeing other posts on the issue, I think more than a generic warning that "may break the image" the Monticello comments and/or a simple explanation on the reasons and affected packages *before* the update starts with an option to proceed or abort is much in need.
Yes, maybe. Then thing is that I am not sure in which cases it would break. Only in overrides? How many overrides do we have from external pacakges in Core stuff? I have no idea.
-- Cesar Rabak
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project