Am Montag, 18. März 2019 21:34:17 UTC+1 schrieb Jason Miller: > > I always have a build script to wrap my tupfile. There are often various > tasks that are not strictly "generate outputs from inputs" that go into > building. > > Since I already have this script, I simply put the VCS revision into an > environment variable, and then the Tupfile can export that when needed. > >> 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.
Julian -- -- 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.
