cache plugin behavior?

[Clark Williams]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael E Brown wrote:
> On Fri, Feb 29, 2008 at 09:58:35AM -0600, Clark Williams wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Michael,
>>
>> I was looking at BZ  233529 on mock and was wondering if the requested behavior seems
>> valid (it does to me, just wanted a sanity check).
>>
>> As far as I can tell, the only time the root cache is invalidated is when it ages out
>> (was looking at the plugin). 
> 
> This is correct.
> 
>> Does it make sense to also invalidate the cache when the
>> .cfg that defines it has a newer modification time?
> 
> Makes perfect sense. May be somewhat difficult to implement, I'm not
> sure we store the config file name anywhere that the plugin can get to
> it. 
> --
> Michael

Here's a way to do it.

One thing that wasn't immediately apparent to me, but became clear when I started
installing/debugging was that everytime you install a new mock rpm, the cfg file will
have a timestamp newer than any existing root-cache file, which means with this patch
each root-cache will be rebuilt. This seems like a reasonable thing to do (rebuild
the caches after installing a new mock), but I wonder if it will break anything?

Clark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkfIY9cACgkQHyuj/+TTEp07nwCeMSIqBL3c8g9BXmr+BisitT2B
g50An2nDwD5xbJ+Nh6Or/ZDDuWwMecxt
=Ht8F
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cache-mod.patch
URL: <http://listman.redhat.com/archives/fedora-buildsys-list/attachments/20080229/da8c7ba8/attachment.ksh>