> > However, this code change makes it so that once updates have arrived, > > you'll never check for any further updates again. Is this really the > > desired behavior? Wouldn't the customer want to know that additional > > updates are available, regardless of how many updates are currently > > outstanding? > > > > We believe that this is the behavior we want > > We do not have the concept of additional updates. We display the icon if > updates are available. > > The only way the icon becomes not visible is for the user to invoke > UpdateManager by activating the icon. This causes updatemanagernotifier > to exit. We discussed this during our code review yesterday and are > satisfied with the behavior. If we were to change the behavior we would > schedule a check for updates after the icon was activated instead of > terminating the process. > > Our assumption is that the user will install some software after > invoking UpdateManager and will reboot the system.
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 case where the user either invokes the updatemanger but decides not to perform an update, or installs software that doesn't require a reboot? It seems like we ought to continue to check for new updates in both of these cases. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
