On Mon, Aug 3, 2020 at 7:08 PM Orion Poplawski <orion@xxxxxxxx> wrote: > > On 7/7/20 12:09 PM, Neal Gompa wrote: > > On Tue, Jul 7, 2020 at 1:57 PM Orion Poplawski <orion@xxxxxxxx> wrote: > >> > >> On 6/15/20 1:47 PM, Ben Cotton wrote: > >>> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds > >>> > > >>> == Upgrade/compatibility impact == > >>> Existing packages can (and most likely will) become FTBFS, but > >>> proposal owners will fix as many Fedora packages as possible. However > >>> fixing third-party packages is not possible and out of scope. > >>> Third-party packagers will need to adapt based on the recommendations > >>> noted in this Change. > >> > >> What's the plan for EPEL8/7 compatibility? > >> > > > > I need to talk to EPEL folks about how to handle this. I'm not sure > > exactly what strategy we should take here. I could override the macros > > entirely with epel-rpm-macros, which is probably the easiest way to do > > it. > > > > Any progress here? This is becoming a large pain point for me. > I implemented a hacky solution last week[1][2]. There's a bug to get RH to update CMake and pull in the proper macros into RHEL 8[3]. [1]: https://src.fedoraproject.org/rpms/epel-rpm-macros/c/3d7bea8322f8a7c5bd1b01ec16180c5b036a65a7 [2]: https://src.fedoraproject.org/rpms/epel-rpm-macros/c/e93d8e2f0d0b056349a22d5bef8a93116d469516 [3]: https://bugzilla.redhat.com/show_bug.cgi?id=1858941 -- 真実はいつも一つ!/ Always, there's only one truth! _______________________________________________ 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