Hi,
in the Pharo images I produce, there is a System->Update that never works. A lot of people are confused by it and don't know it only works on the core. Shall we remove this item from the menu? Bye -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
I just tried it last week and it failed horribly, and yet tried it today and it worked great. I'm new to Pharo and tried it as I was used to updating Squeak frequently. If it's going to work in the future I'd say leave it. If it's part of core only it would be nice to not see it other builds.
- John
|
It would be interesting to understand what exactly the problem is. Has
anybody looked into it? If it is hard to fix, we should disable the update function. When we create an update, we (or at least I) only test with the core image. Adrian On Jul 20, 2009, at 19:24 , John E. wrote: > > I just tried it last week and it failed horribly, and yet tried it > today and > it worked great. I'm new to Pharo and tried it as I was used to > updating > Squeak frequently. If it's going to work in the future I'd say leave > it. If > it's part of core only it would be nice to not see it other builds. > > - John > > > Damien Cassou wrote: >> >> >> in the Pharo images I produce, there is a System->Update that never >> works. A lot of people are confused by it and don't know it only >> works >> on the core. Shall we remove this item from the menu? >> >> -- >> Damien Cassou >> > > -- > View this message in context: http://n2.nabble.com/Shall-we-forbid-updating--tp3289784p3290315.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Mon, Jul 20, 2009 at 6:55 PM, Adrian Lienhard<[hidden email]> wrote:
> It would be interesting to understand what exactly the problem is. Has > anybody looked into it? > > If it is hard to fix, we should disable the update function. When we > create an update, we (or at least I) only test with the core image. I can imagine multiple problems: 1- some packages override some methods of the core which are reseted on update. That could be fixed but would require some work from package maintainers 2- some updates require that no window are displayed (like Polymorph updates) There are probably others -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Damien Cassou
Rehi,
the update more than once saved my day. As I experienced problems with the context menus on vista on latest images, the update function was the only workaround to get pharo acessible at all. Cheers, Andreas Damien Cassou schrieb: > Hi, > > in the Pharo images I produce, there is a System->Update that never > works. A lot of people are confused by it and don't know it only works > on the core. Shall we remove this item from the menu? > > Bye > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |