On Sun, Jan 10, 2010 at 4:56 PM, Michael Roberts <[email protected]> wrote:
> without its own update stream, or section in the update file, I think > the effect of allowing the Pharo image to update itself based on the > core update file would lead to an undefined result? > > Yes. Mostly due to overrides. > If that is the case I would disable it. > > I assume this would be replaced by some Metacello 'update stream' ? > > That's a good idea. I am not sure how to implement it, but for sure, it will be in a future ;) Maybe 1.1 > cheers, > Mike > > 2010/1/10 Mariano Martinez Peck <[email protected]>: > > It is a simple question. Do we allow that or not. Miguel wrote the pros > and > > cons: > > > > Pros > > - Can fix bugs after release > > - Can aply improvements to the image after release. > > > > Cons > > - Can mess the image of someone by overwriting some overridden method. > > - Can accidentally update more than intended in someone's image > > > > > > We have to take a decision. > > > > Cheers > > > > Mariano > > > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
