Missing system dependencies for our Python builds

[michaelmayer2]

It would be good to add more meaningful system dependencies to our python builds. At the moment a user can successfully install python built for RHEL9 on CentOS 7 without any problem but then wonders why pip does not work. One would then get

/opt/python/3.9.15/bin/python3.9: error while loading shared libraries: libcrypt.so.2: cannot open shared object file: No such file or directory

I know that our python builds are opinionated, but it still would be good to add clear dependencies to the RPMs that one could extract at build time like the one below

ldd /opt/python/3.9.14/bin/python | awk '{print $3}' | grep lib64

At the moment I can see

# rpm -qp --requires python-3.9.14-1-1.x86_64.rpm 
libev-devel

which is a bit too small IMHO. I'd expect to see references to libcrypt* and libfreebl* in their respective versions at a minimum.

[edavidaja]

Summarizing a discussion from earlier:

• we're assuming libcrypt will be available
• insisting that libcrypt be available would make it more likely that the rpm will fail to install, rather than installing successfully and then failing at run time.
• we should consider improvements to the design of the install python documentation to reduce the probability that someone ends up with the wrong RPM

[rocky@ip-172-98-0-170 ~]$ ldd /opt/python/3.9.14/bin/python
	linux-vdso.so.1 (0x00007ffd0a75b000)
	libpython3.9.so.1.0 => /opt/python/3.9.14/lib/libpython3.9.so.1.0 (0x00007f47a1704000)
	libcrypt.so.2 => /lib64/libcrypt.so.2 (0x00007f47a16c6000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f47a15eb000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f47a13e2000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f47a1a9c000)