On 18. 04. 19 18:17, Richard Shaw wrote:
I'm working on packaging PySide2 for Fedora[1] and have a couple of questions...
*** Also, I could use an experienced python packager to do the review! ***
1. Should the %python_provide macro be applied to python-<pkgname>-devel
packages? Or just for the main python module package?
Everything that is called python2-foo or python3-foo should be accompanied by
%python_provide. it doesn't matter whether it is "main python module package" or
not.
If the package is called python-<pkgname>-devel (sometimes happens if it is
Python version agnostic) -> no need for %python_provide.
If the package is called python3-<pkgname>-devel, %python_provide should be used.
2. Do I need to filter requires/provides for C python libraries if their not
private?
I always understand it that provided libxxx.so.so.X.Y() are intended to be used
by linkers directly. E.g. Python modules should not provide
libxxx.cpython-37m-x86_64-linux-gnu.so or similar.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
