3 ms·
Every time tup comes up, there's a question I have that nobody seems to know the answer to: how does tup know what changed? Make does this by starting from what
by dima55 12y ago
Every time tup comes up, there's a question I have that nobody seems to know the answer to: how does tup know what changed? Make does this by starting from what it needs to build (which it knows) and traversing the dependencies. Does tup have some sort of daemon that monitors the file system? What if the file system isn't local (NFS, say)?
- foxhill 12y agoi don't know for certain but i'd guess at; for each file specified in tupfile is target output file's creation date older than input file's last modified date? yes -> build, no -> skip.
- xt 12y agoIt uses inotify for file systems that supports it.
- deleted 12y ago[deleted]
- dima55 12y agoSo then it DOES have a daemon? Have you actually tried it? And inotify doesn't work over NFS.
- deleted 12y ago[deleted]
- mbq 12y agoYou can have a daemon (tup monitor), but it is not required; in the second case tup will compare last-mod times of files with those from the last run (stored in the .tup dir).
- dima55 12y agoThank you!