[issue351] rpm-backend: overfrequent cache updates (not repository updates)

[apriori at Labix Tracker]

apriori <apriori at dkc-clan.de> added the comment:

So if I understand you correctly, because you said cache updates are faster if 
there are no changes - the cache is always rebuilt from scratch? Why should 
this be needed?

Maybe I explained incorrectly, so I'll try again. Why should smart run a cache 
update/rebuild if there are no changes done to either the channel files or 
rpmdb (I think just searching for packages guarantees that there are no 
changes)? I give you an direct example, everytime I search for something, I can 
see output like this:

smart search test
Loading cache...
Updating cache...                                           
##################################################################################
 [100%]
----

And the "Updating Cache" here just doesn't make any sense to me, because before 
that search operation neither the channel files nor the rpmdb have been touched.

----------
status: resolved -> chatting

_______________________________________
Labix issue tracker <tracker at labix.org>
<http://tracker.labix.org/issue351>
_______________________________________