> If file "$HOME/project_42_iso_ids" exists, then the lengthy parameter
> is taken from there. It defines a timestamp, a disk GUID, and what else
> might turn out to be in need of being reproduced.
I also understand and appreciate that some use-cases need more entropy
than a 32-bit integer can provide. However, I feel like the parameter you
suggest could quite easily fallback to SOURCE_DATE_EPOCH with the extra
bits -- I use the term hand-wavingly for now -- masked to zero.
Anyone needing to provide more "secure" entropy could then use the
interface you suggest.
Otherwise, I sincerely worry that your efforts to make the output
reproducible will be neglected as the user interface is simply too
complicated.
I agree that an environment variable is not the perfect channel to
communicate values to a process, but this particular now has such
widespread adoption that its becoming somewhat quixotic not to make use
of it.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
