On Fri, Feb 28, 2020 at 4:13 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > On Fri, 2020-02-28 at 20:42 +0100, Miro Hrončok wrote: > > > > > * ...the Shiny New Stuff does not appear to be available on EPEL *at > > > all* yet - not even EPEL 8. This makes it a bit of a non-starter if you > > > want to use the same spec file bits across Fedora and EPEL. I realize > > > it may be impractical/impossible to backport everything to EPEL 7, and > > > am getting close to the point where I throw in the towel and drop > > > Python 2 support from my projects' master branches and hang the EPEL 7 > > > package repos out on a branch, but EPEL 8 would be nice and ought to be > > > possible? > > > > This stands in a way of having this in EPEL 8, AFAIK: > > > > - no automatic RPM buildrequires > > - ancient pip (PEP 517 support was added in 19.0, we have 9.0.3) > > - ancient setuptools (40.8 is needed, we have 39.2.0) > > - no tox (but it's being packaged for EPEL8 as we speak) > > Yeep! I didn't realize we had such ancient bits in 8... > Dynamic BuildRequires is unlikely to make it to RHEL 8, but all the others are achievable if the requests are made, right? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
