On 11/18/08 19:10, [EMAIL PROTECTED] wrote: > I'm not sure I understand what this fix is trying to accomplish. In the > bug report, it says: > > 1) When starting if the update icon is going to be displayed the > is no need to schedule checking for updates. > > 2) When updates have been found there is no need to check for > further updates. > > 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. Padraig > -j > > On Tue, Nov 18, 2008 at 01:48:46PM +0000, Padraig O'Briain wrote: > >> The webrev http://cr.opensolaris.org/~padraig/ips-5188-v1/ removes >> redundant processing in updatemanagernotifier. >> >> See http://defect.opensolaris.org/bz/show_bug.cgi?id=5188 for >> description of the changes. >> _______________________________________________ >> 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
