John Rice wrote: > 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? >
Yes. The problem is this: Suppose there's a package out there that contains files where some require a reboot if changed and others do not (this is usually the case for pkgs that can require a reboot at all). Suppose this occurs between version 4 and version 5... now if the user goes from 2 to 3, no reboot is required, and the same from 5 to 6. But from 3 to 6 a reboot is needed. Note that filters, etc, can change this as well; one can imagine a case where the file requiring the reboot is filtered out on a particular install. Thus, "reboot_required" is a per action (usually file) attribute, and thus whether or not a reboot is required cannot generally be known prior to imageplan evaluation. - 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
