#12 Changed include does not cause "not modified" files changed

[Jason Vogel]

If you change an include file but not the file with the
include AND have the don't touch unmodified file flag set
to true, then the change is not picked up.

Jason

[Dániel Dékány]

Logged In: YES
user_id=546667

That's a documented behaviour (see settings.html, "Skipping
unchanged files"), which admittedly sux. Unfortunatelly it is technically
hard to track these dependencies... it require a separate persistent
dependency storage. I don't think I will implement this in the near future.
For many projects "--skip-unchanged=static" is usable only. And even if I
track #includes (a little FreeMarker hacking needed...), similar problem
occurs when you change the files/databases that store the "data" you
display, which is, in practically, almost impossible to track.

[Jason Vogel]

Logged In: YES
user_id=202974

I completely agree about the database issues. You could
track the filename (including the path) along with the datetime
stamp of file in some sort of config file, and if that file
changes, then the include changes, so the file changes.

I know this is a nice to have, but it's worth considering I
think. Basically, store all store all the include file names,
walk the list to check for changes, and then ...

Just an idea,

Thanks,
Jason