inotify/FindFirstChangeNotification support to minimize md5 hashing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run incremental fabricate.py build.

What is the expected output? What do you see instead?
Minimal md5 hashing, ie, only rehash those files that have changed, not every 
file that is dependent.

What version of the product are you using? On what operating system?
ToT; Windows 8 x64; CentOS 6.3 x64.

Please provide any additional information below.

By adding a (preferably python-only) daemon that runs "on the side" using the 
inotify/FindFirstChangeNotification APIs, it is possible to detect the set of 
files that are written to. These files can have their md5 update automagically 
"on the side". This will preclude fabricate from having to run the md5 hash 
during incremental builds.

Original issue reported on code.google.com by jaros...@gmail.com on 9 Jan 2013 at 6:11

[GoogleCodeExporter]

http://timgolden.me.uk/python/win32_how_do_i/watch_directory_for_changes.html 
would work for Windows. (The last method seems to be the best.)

Original comment by jaros...@gmail.com on 9 Jan 2013 at 6:14

[GoogleCodeExporter]

Changing to an enhancement request

Original comment by simon.al...@gmail.com on 5 Apr 2013 at 10:33

• Added labels: Type-Enhancement
• Removed labels: Type-Defect