Rainer Jung

Thanks! Can one find out the SOURCE_DATE_EPOCH that the project used for its own binary distribution? And doesn't SOURCE_DATE_EPOCH only influence the makensis binary, but not any application installer created by makensis using an nsi file?

Thanks! Can one find out the SOURCE_DATE_EPOCH that the project used for its own binary distribution?

I can't close the ticket, but feel free to close it. Thanks.

It seems we managed to be able to do cross-platform reproducible builds. So I am closing this. We used the following scons line to build the makensis installer (and tool all other files from the same binary download for Windows, that are used when building the installer directly on Windows): scons UNICODE=yes PREFIX=/home/myuser/install/nsis-3.10/bin SKIPPLUGINS=all SKIPUTILS=all SKIPMISC=all NSIS_CONFIG_CONST_DATA_PATH=no VERSION=3.10 install-compiler

Cross-platform reproducable builds

I just ran into a situation, where the minimal integer limit "1" in QS_ClientEventPerSecLimit is a bit too big. I could write a patch supporting non-integer (fractional) limits for the PerSec directives. Since the rates are calculated on a 10 second base, the minimal non-zero request rate is 1 in 10 seconds = 0.1 req/sec. So rounding 10 times the given value to a long might be precise enough. Related: What about making QS_BW_SAMPLING_RATE (10 seconds) configurable too? Making it smaller allows to...

I think this is still valid?

Here are a ew small improvements in directuve declarations. Please double check, whether I am correct. --- mod_qos.c 2022-03-18 12:31:05.130441100 +0100 +++ mod_qos.c 2022-03-19 13:39:59.695950800 +0100 @@ -14320,7 +14320,7 @@ #else AP_INIT_TAKE2("QS_SrvMinDataRate", qos_min_rate_cmd, NULL, RSRC_CONF, - "QS_SrvMinDataRate <bytes per seconds> [<max bytes per second>]," + "QS_SrvMinDataRate <bytes per seconds> <max bytes per second>," " defines the minimum upload/download" " throughput a client must...