[Scons-users] Decider which checks md5 checksums unexpectedly detecting changed/invalid ones

[Tom Tanner (BLOOMBERG/ LONDON)]

Replying to myself:

I think it is a general bug: When the new node is created, it calls get_csig. This calls get_max_drift_csig. Which depending on various things can return the previous cached sig rather than the one from the built / copied from cache object.

This doesn't seem a terribly good idea to me, that after you'd built a brand new object, you'd copy the previous signature over.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20130920/c3a71732/attachment-0001.html