>>>> Why are you so aggressive against us? >>> >>> I didn't mean to be aggressive, I just don't think your idea will work well. >> >> we will see. >> >>>> Now if you want status quo why do you even commit in squeak? >>> >>> I'm not against changes. >> >> So I did not understand. Probably my english. > > I like to keep stuff backwards compatible as long as it doesn't "cost" too > much do it. And I like when my old code works with none or minimal changes in > newer systems.
Us too. >>>> Pharo1.0 is not abandoned at all. Since 1.0 we got more than 1000 bugs >>>> closed. >>>> The versions are just a way to have milestones. Now there is no problem >>>> you think otherwise >>> >>> So if I have a Pharo 1.0 image with my code and I don't want to rebuild the >>> image, then how can I update it to 1.1? >> >> - first I cannot reload code for you. >> - second you can simply look at Utilities and find the right invocation to >> get the next update >> stream. >> >> Something like that >> Utilities readServer: Utilities serverUrls updatesThrough: nil >> saveLocally: true updateImage: true. >> But you should set the version to 1.1. >> >> I'm sure that you can easily find how to do it. > > I tried this in a PharoCore 1.0 image: > > ScriptLoader currentMajorVersionNumber: 1.1. > SystemVersion current version: 'PharoCore1.1ALPHA'. > Utilities readServerUpdatesThrough: nil saveLocally: false updateImage: true. > > But the image freezes (not interruptable by Alt+. (or Cmd+.)). I do not have the time to have a look since we haves ESUG organization now more than ever. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
