This is one of the long term plans that nobody has time to do :) Python packages have INSTALLER file. We should make sure that it is present for our packages and that it says rpm instead of pip. See https://src.fedoraproject.org/rpms/python-pip/pull-request/5 for initial discussion. @torsava: > Ideally, pip install should have a switch to to set what will go into the > INSTALLER file and then we can use this in python-rpm-macros. @churchyard: > Note that we mostly use python setup.py install, not pip. @ncoghlan: > As far as a longer term answer to "How to reliably set INSTALLER > appropriately?" goes, I think it would be better if there was an RPM file > trigger in the base Python package that overwrote the INSTALLER files for > anything installed via RPM at install time. That way it would automatically > do the right thing for all RPM managed Python packages with dist-info and > egg-info directories, whether those packages are old or new, Fedora built, > or third party. > > (Such a file trigger could potentially even synthesise dist-info directories > for packages that don't have them, but doing that would require defining an > upstream convention for reserving a suitable namesspace - pursuing such an > idea would be a lot more feasible now that legacy PyPI has been shutdown).
Most likely a goal for Fedora 31
Let's do this with the %pyproject macros. Already marked as blocked on bz1685582.
%pyproject macros do this, and the old %py3_install macros don't have INSTALLER at all. Let's just keep them as they are.