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. 

Ok, that's what I was trying to get to when I was looking at the plugin. There's
probably something we can stash in the root object that the plugin can get to, maybe
even the full path of the config file. My thought is that if we can get the config
path, it's just stat'ing it and comparing the modification times.

I'll poke at it a bit.

Clark

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

iEYEARECAAYFAkfISE0ACgkQHyuj/+TTEp2AFgCfXOB3gAHBokYqSra6byPe7qsz
R6sAn1kciphuenG3Cu8lsDAcWsxJbxZV
=faMP
-----END PGP SIGNATURE-----