Several ORB tools generate output with embedded timestamps. This makes it impossible to use them in reproducible builds.
While trying to make our system's build reproducible, I ran into the problem that the idl files generated by rmic -idl contain the timestamp of the build moment. This means we can not get the build to reproduce identical binary outputs.
Looking further, I've seen that not only rmic but also idlj and exception-annotation-processor output the build timestamp in their output files' prologues.
The value of the build timestamp within the comments in the file is questionable; however, if they are deemed required, at least the tools should take into account the SOURCE_DATE_EPOCH environment variable spec.
Several ORB tools generate output with embedded timestamps. This makes it impossible to use them in reproducible builds.
While trying to make our system's build reproducible, I ran into the problem that the idl files generated by rmic -idl contain the timestamp of the build moment. This means we can not get the build to reproduce identical binary outputs.
Looking further, I've seen that not only rmic but also idlj and exception-annotation-processor output the build timestamp in their output files' prologues.
The value of the build timestamp within the comments in the file is questionable; however, if they are deemed required, at least the tools should take into account the SOURCE_DATE_EPOCH environment variable spec.