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

[Adam Williamson]

@Conan-Kudo Oh, I'm sure *everyone* who tries to express a dependency like this tries the name 'rpm' first. I certainly did. :P But as you say, that never previously did work, so anyone who's previously tried and not just given up when 'rpm' didn't work must surely have landed on 'rpm-python', like I did. Since that's what the name actually *was*. So if you believe that real world people actually have written projects that express this dependency, you implicitly must believe that they wound up writing code that depends on 'rpm-python'...and thus that this change will *break* that code. As I said above, I agree that in theory the name *ought* to be 'rpm'. I'm not saying 'rpm-python' is a better name than 'rpm'. What I'm saying is that once you've already picked a name, changing it isn't a free action.

If you explicitly want to say "we don't think it's worth caring about people who already figured out and used the old name, or people who want to depend on our built distribution in a way that works with both RPM <= 4.13 and RPM >= 4.14", then...I guess fine, but that seems like a pretty 'go away' kinda position. The ideal solution would be to come up with *something* that will allow both 'requires rpm' and 'requires rpm-python' to work. I think there's probably *some* way to do this, I just don't know what it is yet.

-- 
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-353699694
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20171223/268e81a6/attachment.html>