Could you post a MCVE (minimal complete verifiable example, to borrow from SO parlance) I can think of 2 things that caused unecessary tup rebuilds fro me A) volatile dependent environment variables -- e.g., you always depend on path and things like rvm revel in changing your path -- that change will cause a tup rebuild for all targets whose recipes run something (=all targets) B) convert/compile commands that do a directory scan -- most directory scans on Linux do `open` with `O_DIR` (not sure if that's the right name of the flag) which makes tup think each target depends on every other file
On Thursday, July 9, 2015 at 3:20:49 PM UTC+2, Gerhard Giefing wrote: > > Hi, > > I have a question about tup. > > Tup is deciding by itself, which files shell be updated in a "tup run". > I have a large project where many files need to be converted. I > experienced that (it looks like) all files are converted even if I do not > change a thing in between two "tup runs". > > Does anyone have an idea of what are the basic rules for tup to update a > file, or is there a bug in tup? > > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
