https://bugzilla.redhat.com/show_bug.cgi?id=2254392 --- Comment #3 from kb1000 <kaeptmblaubaer1000@xxxxxxxxx> --- Fixing the first two issues is pretty easy, but the PCRE problem seems to be a bit harder to address. Upstream still doesn't really seem to want to change this or accept a PR, so I'd need to apply the two upstream SWIG commits to the custom SWIG build, but I'm not entirely sure how to do that properly. It seems like it's possible to just set RENDERDOC_SWIG_PACKAGE to a directory instead of a file, but that also means I need to extract both source tarballs. What's the current best practices for packages with multiple sources and patches? I can't seem to find a lot of information about this in the packaging guidelines or RPM documentation. It doesn't look like %autosetup would help me there? Do I have to use %setup and %patch? -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2254392 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202254392%23c3 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
