Overview
Request 1177608 superseded
- Rework packaging to modern python packaging as we need
policycoreutils-python-tools as build dependency for python311-setools
- General:
- python version for scripts is now set to python311, deprecating python3.6
- replaced python3 dependencies with corresponding dependencies
- moved %{_localstatedir}/lib/selinux out of the python-policycoreutils
rpm and into policycoreutils-python-utils as it does not belong
into a module and causes conflicts when module is built for multiple
python versions
- Factory-specific changes:
- python-policycoreutils module is now built for python310, python311,
python312 instead of python3
- added %python3_fix_shebang to set the shebang to the current python
- 15.4 and 15.5 specific changes
- python-policycoreutils module is now built for python311 instead
of python3
- added %python311_fix_shebang to set the shebang to python311, this
is currently a dirty hack since the python3_fix_shebang_path macro
does not exist in <=15.5 so far
- 15.4 specific changes
- policycoreutils-devel requires python3-distro still, as there
is no python311-distro package
Request History
cahu created request
- Rework packaging to modern python packaging as we need
policycoreutils-python-tools as build dependency for python311-setools
- General:
- python version for scripts is now set to python311, deprecating python3.6
- replaced python3 dependencies with corresponding dependencies
- moved %{_localstatedir}/lib/selinux out of the python-policycoreutils
rpm and into policycoreutils-python-utils as it does not belong
into a module and causes conflicts when module is built for multiple
python versions
- Factory-specific changes:
- python-policycoreutils module is now built for python310, python311,
python312 instead of python3
- added %python3_fix_shebang to set the shebang to the current python
- 15.4 and 15.5 specific changes
- python-policycoreutils module is now built for python311 instead
of python3
- added %python311_fix_shebang to set the shebang to python311, this
is currently a dirty hack since the python3_fix_shebang_path macro
does not exist in <=15.5 so far
- 15.4 specific changes
- policycoreutils-devel requires python3-distro still, as there
is no python311-distro package
This is only true on Leap
will change that
%python311_fix_shebang is fine, the dirty hack is needed on top of that (if I understood things right) since on Leap neither does %python311_fix_shebang fix /usr/sbin, nor does %%python311_fix_shebang_path exist
yes thats correct
This is a bit indirect. The net result is that on TW, %python_binary_for_executables will be set to python3 (so it will work due to python3 -> python3.11 on TW). So maybe you could just set %define python_binary_for_executables python3 in the %else case just to be clear.
i would disagree, this way it changes when they change the macro definition
Wait, "export PYTHON" after the line where you expand it and call make?
it builds scripts after that again, thats why i set it back to the python_binary_for_executables
I would just move the contents of this %if into the previous %if, immediately below %python311_fix_shebang
fair point