Am 2020-03-29 um 09:27 schrieb Hervé BOUTEMY:
Le samedi 28 mars 2020 20:56:25 CEST, vous avez écrit :
Am 2020-03-28 um 18:21 schrieb Hervé BOUTEMY:
Hi,

I'd like to announce a new important step for Reproducible Builds for the
JVM: reproducible-central.

The intent is to provide easy to run reproducible recipes, to let anyone
rebuild a component from Central Repository that is expected to be
reproducible and check that the result is as expected.

See https://github.com/jvm-repo-rebuild/reproducible-central for the
current list of project releases that are rebuilt and checked (with
sometime only partial success).

When someone publish a new release that is expected to be reproducible,
don't hesitate to provide a PR with the recipe (= a .buildspec file),
testing it by running "./rebuild.sh path-to-recipe.buildspec" (then
updating README.md by running "./update-reproducibility-summary.sh"


In the future, this little Github repository should become something
better
than a git repository, but this is a first step: improvement ideas
welcome.

The entire approach looks non-portable and absolutely Docker-centric,
confined to Linux distros only. This violates the Java and portability
principle for me.
had a bad week?

The worst is yet to come the next couple of weeks...

the provided recipes are not expected to be the only ones possible to get the
output: they are meant to be a choice on simple way for anyone to execute
them, without having complex setup
Hence my choice of Docker as default rebuild prerequisite.

But you can write your own rebuild.sh equivalent if you want, writing your own
way to setup your local JVM.

I'll try to make this more visible, without introducing too much complexity
into the scripts: one of the intents is also to stay simple

Please update the README by not claiming that it can be reproduced on any Unix with that setup. I creates false expectations.

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to