On Sat, 2020-12-19 at 20:07 +0100, Dan Čermák wrote: > clime <clime@xxxxxxxxxxxxxxxxx> writes: > > > On Thu, 17 Dec 2020 at 22:04, James Szinger <jszinger@xxxxxxxxx> wrote: > > > > > > On Thu, 17 Dec 2020 14:05:40 -0500 > > > Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > > > > > 1. How does this affect users who download, maybe modify, and rebuild > > > the SRPM? Can they continue to use rpmbuid and mock as they have > > > been? Does the SRPM contain the pre-processed or post-processed spec > > > file? > > > > They can use mock if the preprocessing will be enabled for the > > respective chroots where it is enabled in Koji/Fedora. > > They can't directly use rpmbuild for those packages that contain the > > macros. But they can use rpkg/fedpkg to do the work. > > Or preprocess spec first and then use rpmbuild. I am aware this is a > > negative point of this change. > > This is a pretty big downside imho, as that means that building Fedora > packages that use these new kinds of macros in other build systems will > become impossible or at the very least, very, very difficult. There is > quite some development going on in OBS (afaik e.g. Igor exported all > Fedora Rust rpms to OBS for automated rebuilds) and enabling this > preprocessing will make these packages FTBFS in OBS. I mean, only if you're sourcing from dist-git? The .src.rpm will have the post-processed spec file and should rebuild anywhere without issues, presumably. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ 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
