18215274d8
As described inline, deprecate the "source" install for CentOS 8. Overwriting the packaged tools has long been a pain-point in our images, and the best outcome is just not to play the game [1]. However, the landscape remains complicated. For example, RHEL/CentOS 8 introduces the separate "platform-python" binary, which seems like the right tool to install platform tools like "glean" (simple-init) with. However, platform-python doesn't have virtualenv (only the inbuilt venv). So that every element doesn't have to hard-code in workarounds for these various layouts, create two new variables DIB_PYTHON_PIP and DIB_PYTHON_VIRTUALENV to just "do the right thing". If you need is "install a pip package" or "create a virtualenv" this should work on all the platforms we support. If you know more specifically what you want (e.g. must be a python3 virtualenv) then nothing stops elements calling that directly (e.g. python3 -m virtualenv create); these are just helper wrappers for base elements that need to be broadly compatible. [1] http://lists.openstack.org/pipermail/openstack-infra/2019-September/006483.html Change-Id: Ia267a60eecfa8f4071dd477d86daebe07e9a7e38
10 lines
No EOL
344 B
YAML
10 lines
No EOL
344 B
YAML
---
|
|
features:
|
|
- |
|
|
The ``pip-and-virtualenv`` element has added variables ``DIB_PYTHON_PIP``
|
|
and ``DIB_PYTHON_VIRTUALENV`` to make it more straight forward for other
|
|
elements to install packages or create virtualenv environment
|
|
deprecations:
|
|
- |
|
|
Source install for ``pip-and-virtualenv`` is deprecated for RHEL
|
|
8/CentOS 8 |