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

[Adam Williamson]

@n3npq "After reading #273, it isn't clear why a egg-info mechanism tied to pypi"

egg-info isn't "tied to" pypi, just like RPM isn't "tied to" dnf or zypper or yum or Fedora's repositories or SUSE's repositories or Red Hat's repositories.

egg is a "built distribution" format, just like .rpm is a package format. setuptools is a set of tools for producing and working with "built distributions" (and other things), like 'rpm' itself is a set of tools for producing and working with RPM packages. pypi is a repository of built distributions, just like Fedora or RHEL's repositories are repositories of RPM packages. pip is an advanced, dependency-resolving package manager that can retrieve packages from repositories and resolve dependencies between them, like dnf or yum or zypper for RPM packages and repositories.

As I said above, it *is* worth taking into consideration that you've never actually published the built distribution named 'rpm-python' to pypi. It's true that this very likely means far fewer people have interacted with it under that name than would have done if you ever *had* published it to pypi. But by shipping a `setup.py` file which refers to it under that name - which is roughly analogous to shipping a `.spec` file, kinda - you effectively declare the existence of that distribution with that name. Just because you didn't send it to the most widely-used repository of Python distributions doesn't mean it doesn't *exist*.

-- 
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-353699928
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171222/0fd2f02b/attachment.html>