Shawn Walker wrote: > John Rice wrote: >> If we check at startup that the last catalog refresh happened within >> the last 10 hrs then we should be fine (we could have the refresh >> task store this last update time for us in gconf if need be). If it >> has not then we can refresh the catalog on startup. If we want to >> make sure things are ok for a long running package manager, we just >> repeat the check once a day as you suggest and if the cron job is >> operational we will never need to do the refresh as its been done for >> us. >> 0.30 9.30 12.30 18.30 21.30 > > If we make this change in the gui, the cli should be changed too, or > alternatively, we should consider changing the API. > > I don't like the idea of our clients having divergent behaviour in > this area. I agree - both clients should be able to benefit from this.
If the api can do a check for last refresh < 10 hrs ago and/or update service running that would be the best solution. If the check fails we do the catalog refresh for the api operation in the CLI or GUI. The check should be fast and have little impact, so could be run at the start of the api calls that currently trigger the refresh. This would then be the default behavior unless refresh=False. > > Maybe we could add an image property to control this and have the api > respect that unless refresh=False? > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
