From 195c5e0925a4d8215edec96d4c7030ac6feccc2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9mi=20Verschelde?= Date: Tue, 5 Mar 2019 23:06:24 +0100 Subject: [PATCH] Move YEAR definition to version.py If it needs to be hardcoded (for the sake of reproducible builds), it should be together with the other hardcoded version info. And yeah, two months in, let's move to 2019. --- methods.py | 2 +- version.py | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/methods.py b/methods.py index 2d4dc4921f4..7465962187c 100644 --- a/methods.py +++ b/methods.py @@ -55,7 +55,7 @@ def update_version(module_version_string=""): f.write("#define VERSION_STATUS \"" + str(version.status) + "\"\n") f.write("#define VERSION_BUILD \"" + str(build_name) + "\"\n") f.write("#define VERSION_MODULE_CONFIG \"" + str(version.module_config) + module_version_string + "\"\n") - f.write("#define VERSION_YEAR " + str(2018) + "\n") + f.write("#define VERSION_YEAR " + str(version.year) + "\n") f.close() # NOTE: It is safe to generate this file here, since this is still executed serially diff --git a/version.py b/version.py index 17be1554649..0d85b83b8da 100644 --- a/version.py +++ b/version.py @@ -4,3 +4,4 @@ major = 3 minor = 1 status = "beta" module_config = "" +year = 2019