[Rpm-maint] [rpm-software-management/rpm] Obsoleted-by: would be useful in some cases (#1768)

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

> My being able to build hwloc2 with an Obsoleted-by: hwloc > 1 would achieve this.

No. It doesn't matter. Your package doesn't even depend on `hwloc1` but rather `libhwloc.so.5()(64bit)`. What you want is the development headers associated with that library to still be available.

> And this is the problem. I am not the distro vendor. I am a third-party software supplier. I cannot influence how the distro packages and can only influence how I package but am missing the tools (Obsoleted-by: hwloc > 1) needed to seemlessly integrate with the distro. I am also not going to get the distro vendor to support that older release by supplying a backport for it, so I have to do that myself. But I need to be able to do it in such a manner that it integrates with the distro seemlessly.

This is the wrong attitude to solve this problem. As an ISV myself, I have had decent engagements with Red Hat on matters like this in the past. If you don't talk to them about it, they'll never even know that it's a problem.

> IMHO, RPM needs to not only support the distro vendor but needs to provide the tools necessary for third-parties (i.e. non-distros) to integrate into the distro.

RPM upstream is distro-agnostic, we provide all the tools, it's up to the distro to offer them or use them.

-- 
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/1768#issuecomment-914385735
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20210907/9af18482/attachment.html>