On 1/15/22 12:22, Andrew C Aitchison wrote:
On Sat, 15 Jan 2022, Miro Hrončok wrote:python-pytest-cov is something I've lobbied has no business in an enterprise distro at all.... ...As for EPEL I strongly suggest not to introduce python-pytest-cov either. If your package depends on it, please drop the dependency instead, see https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_lintersIn %check, packages SHOULD NOT run “linters”: code style checkers, test coverage checkers and other tools that check code quality rather than functionality. Agreed. Linters do make sense in upstream CI. But not in Fedora. Not inside Fedora *packages*, but if these tools are not available to those using RHEL, Fedora or EPEL is that a suitable platform for CI or for developers ?
No, but that's why it will be provided in EPEL :) -- Orion Poplawski he/him/his - surely the least important thing about me Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
