How to cancel loading updates
dway at mailcan.com
Sun Jul 3 18:07:13 UTC 2005
On Jul 2, 2005, at 8:14 PM, Avi Bryant wrote:
> On Jul 3, 2005, at 2:10 AM, Doug Way wrote:
>> Yeah, I think it'd be easiest to do it this way. It doesn't look
>> like I have permissions to delete the current 39a package or start a
>> new one (you have to be an admin), so if you could that, that'd be
> Ok done.
Ok, I've added the fresh new packages to the 39a project. I renamed
the old #Squeak3.9alpha stream in updates.list to #Squeak3.9alphaold,
and started up a new #Squeak3.9alpha stream, and started adding
I decided I should at least put up a warning dialog for people who have
existing 3.9alpha images following the old stream (which diverged
considerably from 3.8), telling them that they probably need to start
over. I added this update as 6670, the first update in the new
3.9alpha stream. (I then added the Reorg as 6671.)
One problem is that the warning offers to stop the updates for those
people (which is the sensible thing for them to do). But I couldn't
find a good way to bail out of the current updates process without
proceeding to the next update. Is there a good way to do this?
Terminating & restarting the current UI process would be acceptable...
the exact equivalent of typing cmd-. and closing the pre-debug window.
Is there a good DoIt for this? (This is not something we'd normally
do... but in this case I just want to tell people gracefully that their
image is at a dead-end and not force them to continue updating, which
will almost surely break things.)
You can try updating from an old 3.9alpha image to see this in action.
(Another alternative is to abandon the 3.9alpha stream and start the
new one with a new name, such as 3.10alpha, or 4.0alpha. (Like we did
with 3.3alpha.) Then this particular problem goes away. But that
seems like an extreme measure, there isn't really much in the old
3.9alpha, I'd rather just start it over.)
Anyway, while waiting for feedback on this, I'll go ahead and finish up
the rest of the updates including the MCConfiguration update, so that
we have an official 3.9a partitioned image to work with.
More information about the Packages