On Fri, Mar 29, 2019 at 02:55:10 -0700, Julian Stecklina wrote: > We have the same solution at the moment and that results in stale git > revisions being embedded in the build. Wrapping the tup command with > another script also feels "wrong". There should be a way to include git > revisions or build times into the binary that is being built.
The problem here is that Tup wants to know *all* dependencies and outputs and have them specified. Here, your inputs are basically the `.git/HEAD` (plus maybe `.git/index`) and all tracked files for determining the git hash. It's a similar reason why extracting a tarball isn't really supported: Tup wants to know all files that will be written when extracting it. I think I've seen that the external script which sets an envvar or something typically be used on this list. --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.
