Bart Smaalders wrote: > [EMAIL PROTECTED] wrote: >> It seems like there are better ways of determining this information, >> instead of looking through all of the manifests, and examining the size >> attributes. >> >> The pkg client doesn't know how large an install will be until it has >> evaluated an imageplan. Once the evaluation has completed, we actually >> have the number of packages and bytes available. It seems like it would >> make more sense to plug at the end of imageplan.evaluate, than it would >> to do really slow and painful things. You could always prompt the user >> to abort between the evaluate and the download phases. > > This is the only place you can know whether a reboot is needed, or if > critical services need to be restarted, etc. The path taken for upgrade > depends on the starting point, largely _UNLIKE_ today's system (modulo > minimization).
Thinking forward to future GNOME applet GUI that looks for updates and notifies the user, I think this would be just fine and would represent the same as what Windows and MacOS X do. By the time you see those GUI's their equivalent of imageplan.evaluate must already have been run because they are showing you what downloads you need to get current. I imagine our future "keep-up-to-date" applet would be running imageplan.evaluate before it gave the popup to the user saying what was out of date and needed updating. This means it can allow the user to see if a reboot will be required or not. -- Darren J Moffat _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
