[Rpm-maint] [rpm-software-management/rpm] Python module's name changed unnecessarily, making it impossible to express dependencies on it (#373)

[Neal Gompa (ニール・ゴンパ)]

@AdamWill The issue that I've been seeing is that people have been putting `rpm` as the setuptools `install_requires`, which obviously never worked before.

In addition, many Linux distributions (RPM-based and not) didn't install the Python bindings via `setup.py` and didn't provide the metadata anyway. That meant that even if you *wanted* to, it wasn't going to work anyway.

While I've been gradually going and fixing this and making sure that packages providing the python bindings actually install via setuptools, I've also encountered enough things and people who expected `pip` to register it as `rpm`, just as CPAN registered `RPM`, `RPM2`, or `RPM4`, and other language bindings also use the `rpm`/`RPM`/`Rpm` name depending on the convention of the ecosystem.

In all honesty, I think this is a correction that needed to happen.

As for Jun's pybindings installer, it was necessary because we refused to publish the bindings to PyPI (see #273). It would have existed regardless of the name in setuptools metadata...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/373#issuecomment-353698643
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171223/f8ed2ee5/attachment.html>