Well - its clear that the only way for us to get the information we need to display to them about size of the upgrade is to use UMNotifier after its done its scheduled refresh to do an evaluate and cache the results for the fmris that can be upgraded. Then the UM GUI can consume this cached data and present it to the user on startup with minimal delay.
How will information such as reboot required, this package is part of an incorporation etc... be exposed after evaluation? Will we just get this from the info object if we request it after evaluate? JR 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). > > - Bart > > Bart Smaalders Solaris Kernel Performance > [EMAIL PROTECTED] http://blogs.sun.com/barts > "You will contribute more with mercurial than with thunderbird." > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
