On Tue, Jul 16, 2019, 3:48 PM Miro Hrončok <mhron...@redhat.com> wrote:
> Hey, > > when RHEL 7.7 will be released, the following new components/packages will > be > provided (assuming from 7.7 beta): > > python3 - the Python 3.6 package > ================================ > > This new RHEL7 component builds several subpackages, all obsoleting the > subpackages of epel7 python36 package. > We will simply retire python36 from epel7. > > python-rpm-macros > ================= > > This new RHEL7 component is a drop-in replacement of python-rpm-macros > from > epel7, we will simply retire the package. python-epel-rpm-macros already > provide > the necessary macros for python34 in epel7. > > python3-setuptools > ================== > > This new RHEL7 component produces the python3-setuptools package that > obsoletes > the python36-setuptools package (built from the python3-setuptools epel7 > component). > > We cannot simply retire python3-setuptools from epel7, as it also builds > python34-setuptools in epel7 and there is no replacement for that in RHEL7. > > Easiest thing would be to stop building python36-setuptools and only keep > python34-setuptools in epel7, however IIRC we cannot have the same > component > name as in RHEL. If that is indeed the case, python3-setuptools needs to > be > retired and a new python34-setuptools component needs to be created in > epel7. Is > my assumption correct? > > python-pip > ========== > > This new RHEL7 component produces the python3-pip package that obsoletes > the > python36-pip package (built from the python-pip epel7 component). > > The python-pip epel7 component also produces python34-pip and python2-pip > (neither available in RHEL 7.7). > > If my previous assumption about components with RHEL names is correct, we > need 1 > or 2 new components for python34-pip and python2-pip - either we have each > in a > separate component or we create a new component that builds both (called > python-pip-epel maybe?). > > python-wheel > ============ > > This new RHEL7 component produces the python3-wheel package. > > The python-wheel epel7 component produced python-wheel package (Python 2). > > The epel7 package was adapted to produce python2-wheel and python36-wheel, > however there was no successful build of this in epel7. > > If my previous assumption about components with RHEL names is correct, > we need to add a new python2-wheel component to epel7. > > ------------ > > Are my assumptions correct? > > If we indeed need new packages/components, I can help to create them, but > I do > not intent to maintain them. Any takers? > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > _______________________________________________ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org >
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org