Shawn Walker wrote:
I completely agree that its still confusing as heck though. Which is why we've talked about making image-update (as an example) perform an 'immediate' implicit refresh instead of an 'if-it-is-time' because an operation such as that is long-running anyway.
I think having 'image-update' do it an 'immediate' refresh makes sense.
If you can suggest ways that we can make this clearer (in terms of client behaviour; we're aware documentation and configuration interface is still lacking), I'd be happy to hear them.
Maybe the command could say when the catalog cache was last updated if no updates were found.
I should also note that, eventually, repository operations will be able to provide the default value for clients instead of it being hard-coded in the client. For example, if you ran an 'on-nightly' repository, you'll be able to set refresh_seconds=0, and all clients connecting to your repository (assuming they haven't overridden this) will always connect and check for new catalog data when an implicit refresh is triggered.
That actually sounds like the real solution here. -- Darren J Moffat _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
