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

Adam Williamson notifications at github.com
Fri Dec 22 22:52:30 UTC 2017


Please stop focusing on my specific use case here. The point is, you're providing a library, and its metadata for Python distribution purposes is significant, and it's a really bad idea to just change its name in that metadata purely for purposes of 'neatness' or predictability when you've *already shipped it under the other name* for a long time. You can't possibly know how many people have chosen to use the module and express a dependency on it via some mechanism that uses this metadata, and however many people like that there are, this change inconveniences *all of them*.

But to satisfy your curiosity, as it happens, I was not using `rpm` to parse NEVRAs. My code still uses `hawkey` for that, as it happens. I was using `rpm` to do version comparisons on the parsed NEVRAs, because hawkey's code for doing that was [completely broken for a time](https://github.com/rpm-software-management/libdnf/issues/125). Since that bug's been fixed in hawkey (libdnf) now, I've changed my code back to using hawkey for the version comparison too, which means I can drop the use of `rpm` entirely and not care about this mess. But that only solves the problem for *me*. It doesn't solve it for anyone else who happens to be in the same situation.

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


More information about the Rpm-maint mailing list