Sent from my iPhone > On Aug 29, 2019, at 12:58 PM, Kamil Dudka <kdudka@xxxxxxxxxx> wrote: > >> On Tuesday, June 4, 2019 9:43:53 AM CEST Panu Matilainen wrote: >>> On 6/4/19 9:56 AM, Daniel Mach wrote: >>> >>> Dne 31. 05. 19 v 2:15 Pavel Raiskup napsal(a): >>> >>>>> On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote: >>>>> >>>>> Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a): >>>>> >>>>>> If we did this, wouldn't it make it very difficult to use tools like >>>>>> mock on RHEL / CentOS 7 to build for Fedora 3x? >>>>> >>>>> >>>>> >>>>> Speaking of Mock: >>>>> Either the RPM on host need to understand the new format/compression >>>>> **or** >>>>> the packages in @buildsys group (including transitional deps) have to >>>>> be in >>>>> old format - then you can build for Fedora 3x using bootstrap feature. >>>> >>>> >>>> >>>> I need to underline this, it would be really really really bad if we >>>> were >>>> not able to --installroot fedora chroots at least on RHEL 8. How likely >>>> is a backport of zstd support into RPM in EL7+? >>> >>> RHEL 8 should be quite easy - get zstd package into RHEL and recompile >>> rpm with zstd support. >>> >>> RHEL 7 is a different story. The patch doesn't apply directly and a >>> backport would be needed. >>> >>> Panu, >>> how difficult it would be to backport the zstd support to RHEL 7 RPM? >> >> >> Technically, backporting rpmio backends is almost trivial, even to much >> older rpm versions. >> >> Getting new features into older RHEL is a much bigger problem. >> >> - Panu - > > Has there been any progress on this? > > What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 With “mock”, available from EPEL. _______________________________________________ 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
