PEL: setup.py: Check for version in env var
In order to allow pel-message-registry package to have incrementing
versions without having to change the version manually every time the
code changes, check for the version to use in a PELTOOL_VERSION
environment variable. If it isn't present, just use a default version
of 1.0.
The plan is that build tools will call setup.py with the env var set to
a version based on the tag of the openbmc build they are being pulled
into. This has the added bonus that it allows people to know which BMC
code level the tool matches up with.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I38bed9e8a5d1d1b1a6bd1b3decff3eed5b3b6b0b
diff --git a/extensions/openpower-pels/setup.py b/extensions/openpower-pels/setup.py
index c04678e..1ed8fa9 100644
--- a/extensions/openpower-pels/setup.py
+++ b/extensions/openpower-pels/setup.py
@@ -18,7 +18,7 @@
setup(
name="pel_message_registry",
- version="1.0",
+ version=os.getenv('PELTOOL_VERSION', '1.0'),
classifiers=["License :: OSI Approved :: Apache Software License"],
packages=['pel_registry'],
package_data={'': ['message_registry.json',