[EMAIL PROTECTED] wrote: >>> This assumption seems overly simplistic. What happens if the notifier >>> determines that one package is available for upgrade, but the >>> updatemanager isn't invoked until later? Does the updatemanager >>> double-check to see if more updates have arrived? What happens in the >>> >>> >> updatemanagernotifier just determines if there are updates. >> >> When updatemanager is run it determines what updates are available. >> > > Ok. Thanks for clarifying this point. > > >>> case where the user either invokes the updatemanger but decides not to >>> perform an update, or installs software that doesn't require a reboot? >>> >>> >> In both of these cases the user will not receive a notification until they >> next log in (and restart updatemanagernotifier). >> >> >>> It seems like we ought to continue to check for new updates in both of >>> these cases. >>> >>> >> We will reconsider this. >> > > This is my primary concern. Not all updates will require a reboot. It > seems like we ought to continue to check for updates if we successfully > installed the available updates but weren't required to reboot. > I believe currently, UpdateManager only allows a image-update, and not an install of specific package upgrades. This means that currently, a reboot will be required after update. While both of these behaviors will change in the future, I'm not certain that the current UMN behavior is incorrect given those constraints.
Brock > Thanks, > > -j > > _______________________________________________ > 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
