On 04 Nov 2013, at 08:26, Marcus Denker <marcus.denker@inria.fr> wrote:
On 04 Nov 2013, at 00:01, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
But marcus we are doing update all the time because this is the way we push new updates daily. So I do not understand why this would be different?
It happens due to strange things: updates that access the web and URLs change, for example. Or in the past one problem was that it could overload squeak-source to load for hours and hours packagesâ¦
And it takes quite some care to keep it going: when *really* bad things happen, we now (once or twice in a year) upload a fixed image that is than taken as the base. If you want to support âtake pharo2 and update it to pharo3â, (or even, take Pharo3 half a year agoâ¦), then we need to put *a huge* (very huge) effort into making sure that we never ever upload a hand-fixed image. This is a lot of work.
And in addition, even that does not guarantee anything: you would need to actually test itâ¦
So in the end, when we get the the bootstrap into Pharo4, this would even mean that keeping an incremental updater would be completely additional work. Like they do with Chrome⦠I am sure one could generate the diff automatically and detect the cases when it does not work (and tell the user). Would be an interesting research project. Marcus