https://bugzilla.redhat.com/show_bug.cgi?id=1824848 --- Comment #2 from Kelly Brazil <kellyjonbrazil@xxxxxxxxx> --- Ah, I see. I can provide a spec, but I think the challenge will be with a SRPM. Since this is a python3 app, typically users use pip to install it and the source-code is freely available on pypi.org and github. For a python app, can I just create an SRPM that includes the tgz distribution file that I build for pypi? Then I would expect the user to run pip to install it manually. I'm not keen on recreating pip's functionality within a SRPM, so I'm trying to find the best practice here. The examples I have seen for python apps don't seem to fit the modern way of distribution - requiring manual creation of a wrapper script to execute the application. This should be handled by pip. Should I just add `BuildRequires python3 and python3-wheel` to the spec so pip is available and can 'install' the python source? -- 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 -- 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
