On 16/12/2025 07:07, Hervé Boutemy wrote:
+0 could not rebuild the release and get the exact same output, as previous
releases
https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/commons/commons-daemon/README.md
not a blocker, I'll just ask a few questions on key differences between
reference output and my build output, so we can define if there is some easy
change to do in the future:
1. reference commons-daemon-1.5.1-native-src.tar.gz (and other sources) contain
│ │ --rwx------ 0 root (0) root (0) 49482 2025-12-11
12:00:00.000000 commons-daemon-1.5.1-native-src/unix/support/config.guess
│ │ --rwx------ 0 root (0) root (0) 35406 2025-12-11
12:00:00.000000 commons-daemon-1.5.1-native-src/unix/support/config.sub
│ │ --rwxr-xr-x 0 root (0) root (0) 147746 2025-12-11
12:00:00.000000 commons-daemon-1.5.1-native-src/unix/configure
are these 3 files expected to be in the archive, they are not in Git:
https://github.com/apache/commons-daemon/tree/master/src/native/unix
Yes. That is intended. See the "Create native build scripts" section in
HOWTO-RELERASE.txt
2. commons-daemon-1.5.1-javadoc.jar contain legal/ADDITIONAL_LICENSE_INFO and
legal/LICENSE that I don't have in my rebuild: is there a way to get them
built? a Maven profile?
Those are created as part of the Javadoc. The structure of the Javadoc
will vary considerably depending on which version of Java you use to build.
3. commons-daemon-1.5.1-bin-windows.zip contain:
│ --rwxr-xr-x 2.0 unx 155544 b- defN 25-Dec-11 12:00 amd64/prunsrv.exe
│ --rwxr-xr-x 2.0 unx 186776 b- defN 25-Dec-11 12:00 prunmgr.exe
│ --rwxr-xr-x 2.0 unx 127896 b- defN 25-Dec-11 12:00 prunsrv.exe
that i don't get in my rebuild: is there a way to get them built? a Maven
profile?
Those cannot be built via Maven. They get built first, placed in the
right place and then the Maven build picks them up.
See the "Native build" section of HOWTO-RELERASE.txt along with
src/native/windows/README.txt for more detailed instructions.
nothing blocker, just the right time during the vote to see what is just an
improvement of build instructions, what is just a future small fix
The native build for Windows is a whole lot easier than it used to be
now that it uses the 'Static Hybrid CRT' approach.
The docs are enough to remind me how to complete a release build but I
have the benefit of having done it before so there may be gaps in the
docs that I don't even see.
I'll try and improve things but happy to answer any further questions.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
