| Message ID | 20221103173729.875233-1-richard.purdie@linuxfoundation.org |
|---|---|
| State | Accepted, archived |
| Commit | 74fb6539dd06acb0dd6a9af4809152975e8473e6 |
| Headers | show |
| Series | bitbake.conf: Drop export of SOURCE_DATE_EPOCH_FALLBACK | expand |
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 62cdd9aa9c2..a1f0f624e9c 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -676,7 +676,7 @@ export PYTHONHASHSEED = "0" export PERL_HASH_SEED = "0" export SOURCE_DATE_EPOCH ?= "${@get_source_date_epoch_value(d)}" # A SOURCE_DATE_EPOCH of '0' might be misinterpreted as no SDE -export SOURCE_DATE_EPOCH_FALLBACK ??= "1302044400" +SOURCE_DATE_EPOCH_FALLBACK ??= "1302044400" REPRODUCIBLE_TIMESTAMP_ROOTFS ??= "1520598896" ##################################################################
Whilst SDE definitely needs to be exported, the fallback does not as it is only used in our python code via the datastore. It was introduced as an export in 9a1dde74e794362399193dc3f81c9685a83d0776 but even then it doesn't look like it needed to be, likely just a copy and paste mistake. Drop the export. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)