hboutemy commented on PR #745: URL: https://github.com/apache/directory-scimple/pull/745#issuecomment-2658465619
another explanation to this case: if you find in output something that will have to be extracted from reference output to reproduce the exact build, you need to question "why did I store this data in output initially?" if it's "just because it was free, then why not: the more data, the better tracking": this approach is very good, or more exactly "was", I did it in the past (storing username and hostname from the builder, for example: who did that build and where?). But this approach is an approach from "before Reproducible Builds", when output binaries were just opaque boxes where we were trying to inject human data to have a chance to know what is in the jar that we found on a filesystem anywhere, and we don't want to trust just the file name to guess what is really contains. With Reproducible Builds, tracking strategy has completely changed: now, we check the binary content "is it the expected content?" environment-specific markers that we put in the past to try to track are now noise that make our Reproducible Builds life harder -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
