On Sun, Mar 19, 2023 at 10:35 AM Miro Hrončok mhroncok@redhat.com wrote:
On 19. 03. 23 14:36, Neal Gompa wrote:
On Sun, Mar 19, 2023 at 9:23 AM Josh Boyer jwboyer@redhat.com wrote:
On Fri, Mar 17, 2023 at 9:44 PM Orion Poplawski orion@nwra.com wrote:
Pythno 3.11 and some modules have appeared in CentOS Stream 8 appstream. However I don't see python3.11-devel and the other modules that are in CentOS Stream 9 crb in CS8 powertools. I do see them in CS9 koji.
Is this just an oversight or some kind of lag? Or is this intentional? It will make it impossible for EPEL to build needed modules for EPEL 8.
Didn't the EPEL project just remove all modules and declare modularity defunct?
https://fedoramagazine.org/epel-8-modularity-is-going-away/
Your question seems fine otherwise, but this seems to have no impact on EPEL as far as I can tell.
EPEL 8 consumes RHEL 8 via an internal recompose that demodularizes out all non-conflicting modules and imports them so that Koji exposes them for packagers to build against. This means that all Python versions are available for EPEL 8 packagers.
I forgot they flattened the modules. Thank you for the reminder.
Agreed, EPEL 8 can build RPM packages against Python 2.7, 3.6, 3.8, 3.9 and soon 3.11 without RHEL modularity. The fact that some of those are a modular streams in RHEL 8 is successfully abstracted away in EPEL 8.
Python 3.11 will not be a moduluar stream in RHEL 8 anyway but as far as EPEL 8 packagers are concerned, there will be no difference (except bugs or lack thereof).
I believe that Orion simply meant "Python modules" as in "libraries you can install and import from Python" which was a term long before folks invented a different meaning of the word "module".
Gotcha.
josh