On Wed, May 14, 2014 at 13:03:38 -0400, Pat Pannuto wrote: > Hmm.. good point. My next best suggestion for a workaround would be to install > a post-commit hook that writes the hash to a header file.
That's not going to work if you want a flag whether the tree is dirty as well. I think the solution is to have the ability to tell Tup "this command should *always* run; ignore anything it reads" because that's the only sane thing to do for something like this. Also, what do you do for tarballs where git isn't available? Usually you use a .gitattributes to have git archive embed the hash and then use that (if it's available). --Ben -- -- 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.
