The problem is that Adrian said and more: 1) Update stream only manages Core packages. The packages you have in the Core image that are found in the Pharo squeaksource repository. PharoDev is build on top of PharoCore and loads external packages which have their own maintainers.
2) When we change something in PharoCore, suppose we rename or remove a method, all senders are fixed for example. Here the scope is Core, not external packages. This is a task of the external packages developers. 3) When you update your image, it will bring the new version of the new package. Now...suppose the update stream renamed the method String >> contact: to contactTo: The fixes of core packages will be automatically updated. But what happens with the external code that was using (senders) contact: ?? -> lots of DNU Even worst...the overrides. Most of the times, they are evil, but they still exist. Suppose an external package XXX that defined String >> contact: with category *XXX and do something different. When you load such package, the method is overridden. But then, if you update a new version of such package from the update stream, it will be put again the original one. This leads problems difficult to debug and trace. All these continues with people reporting problems, people trying to debug and understand problems...etc....in summary: a wast of time. PharoDev are quite periodically. So, wait and get a new version of the Dev image. Maybe in a future this whole thing may be fixed and the update stream can handle external dependencies too, but I think this is not very easy. Cheers Mariano On Tue, May 25, 2010 at 11:11 PM, Stéphane Ducasse < [email protected]> wrote: > not really :) > we prefer to keep it but that the user cannot use it by accident. > > Stef > > On May 25, 2010, at 11:07 PM, Guillermo Polito wrote: > > > Should that method be deprecated in the current Dev Image so no one makes > a mistake? I don't know how the current "branches" are mantained to allow > something like that... :/ > > > > 2010/5/25 Carla F. Griggio <[email protected]> > > :O > > So I guess that's why it actually didn't update anything... :P > > > > > > On Tue, May 25, 2010 at 5:15 PM, Adrian Lienhard <[email protected]> > wrote: > > The reason why we have turned it off is because updating Pharo images > repeatedly caused problems (in contrast to PharoCore). People then reported > issues. Unless this feature is working properly, we shouldn't enable it > again. One possible cause of the problems are overrides by external packages > in core code. But I think nobody has analyzed the problem in depth so far. > > > > Cheers, > > Adrian > > > > > > On May 25, 2010, at 21:48 , Carla F. Griggio wrote: > > > > > That annoyed me too. Shouldn't that option be checked by default? > > > > > > On Tuesday, May 25, 2010, laurent laffont <[email protected]> > wrote: > > >> World Menu -> System -> Software Update > > >> Cheers,Laurent Laffont > > >> > > >> http://pharocasts.blogspot.com/ > > >> http://magaloma.blogspot.com/ > > >> > > >> > > >> 2010/5/25 Guillermo Polito <[email protected]> > > >> > > >> > > >> I'm sorry but i can't find how to update my 1.1 image. Can I update my > image with this changes? Can someone enlight me? :) > > >> > > >> Guille, the newbie > > >> > > >> > > >> > > >> On Mon, May 24, 2010 at 5:16 PM, Stéphane Ducasse < > [email protected]> wrote: > > >> 11371 > > >> ----- > > >> - Issue 1281: Button in TestRunner to fileout the test results. Thanks > Laurent. > > >> - Issue 2468: Better method trailer method creation. Part One. Thanks > Igor. > > >> - Issue 2406: MovieMorph should be removed from the core. Thanks > Alain. > > >> - Issue 2467: AlllocationTest#testOutOfMemorySignal fails. Thanks > Laurent > > >> - Issue 2331: Reuse test unload - Now there is an SUnitUnloader. > Thanks Guillermo. > > >> > > >> Stef > > >> _______________________________________________ > > >> 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 > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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
