News for hackers. Stuff that matters.
Re:The Tup Build System by dima55 on Friday October 31, 2014 @04:59PM (#8541105)
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)?
Re:The Tup Build System by mbq on Friday October 31, 2014 @08:04PM (#8541714)
You 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).
Re:The Tup Build System by dima55 on Friday October 31, 2014 @10:50PM (#8542039)
Thank you!
Re:The Tup Build System by xt on Friday October 31, 2014 @05:20PM (#8541193)
It uses inotify for file systems that supports it.
Re:The Tup Build System by dima55 on Friday October 31, 2014 @07:47PM (#8541650)
So then it DOES have a daemon? Have you actually tried it? And inotify doesn't work over NFS.
Re:The Tup Build System by foxhill on Friday October 31, 2014 @05:16PM (#8541185)
i 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.