https://bugzilla.redhat.com/show_bug.cgi?id=1981995
--- Comment #3 from Jerry James <[email protected]> --- Thank you, Miro and Karolina. I appreciate the input. I have used %pyproject_buildrequires before, but have come to dislike it for this reason: it becomes difficult for me to figure out what the package needs at build time, which makes it hard for me to manage trees of dependencies. I often ask the question, "Do I still need this package?" With explicit BuildRequires, a simple grep can answer that question. With %pyproject_buildrequires in use ... I don't know how to answer that question. I have to go rummage through koji build logs. It takes a lot more effort. I am thinking seriously about removing the %pyproject_buildrequires I already have in my spec files. If you can give me a simple alternative, I'll consider it. Otherwise, I don't want to add any more uses %pyproject_buildrequires of packages I maintain. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
