Hi,
I'm working on adding pybind11 to RHEL 8 and so I wanted to let you, the
EPEL maintainer, know what's coming.
I'm preparing pybind11 for a new Python stack in RHEL, so it will not
conflict in name or files with your subpackages `python2-pybind11` and
`python3-pybind11` (for Python 3.6) because their files are namespaced
with the Python version.
However, as the pybind11-devel package has files that are not namespaced
with the Python version, the devel package in RHEL *will* conflict with
the files of yours. I have added a conflicts tag so this is handled
properly by yum.
The most important thing to note is that the RHEL pybind11 packages will
be in a non-default stream of a module in the CRB repo. Users will have
to enable both the CRB and the module/stream explicitly to see the packages.
Therefore, I belive you don't need to take any action and can keep your
package as is, even after pybind11 is released in RHEL.
The relevant guidelines rule [0]:
"In EPEL8 or later, it is also permitted to provide an alternative
non-modular package to any package found only in a non-default RHEL module."
[0] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy
All the best, and let me know if you have any questions,
Tomas Orsava
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
