On Fri, May 16, 2014 at 3:16 PM, Matthias Vegh <[email protected]>wrote:

> I'm a colleague of the original poster, and have spent the majority of
> today trying to get this work. It can be done, but requires a gruesome hack.
>
> My first attempt was to add an environment variable to the mix, one that
> always changes, and would influence the rule that generated the git hash.
> Seeing as various shells provide such a variable-like thing ($RANDOM) I
> started there. It turns out, that $RANDOM is not exactly an environment
> variable.
>
(I'm not sure how exactly, but tup couldn't export it).
>
Can you assign $RANDOM to MYRANDOM and export that?

Something about all programming problems can be simplified by the addition
of an extra level of indirection.

-- Lee

-- 
-- 
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.

Reply via email to