> i can share the sources with the developer of this software so it allow them to fix it for me
But is that realistic? Will you be able to convince a third-party to work with RHEL code if they can't actually install a system themselves? You could provide the code for the errant library, but to really test it, the developer would probably like to try it on a full RHEL system. And if that is now difficult to do w/o a RHEL subscription, what's the third-party developer to do?
What you'll find is a slow migration away from third-parties supporting RHEL. I'm not sure what the end game here is for IBM, but it makes the entire ecosystem significantly more difficult to work with.
But is that realistic? Will you be able to convince a third-party to work with RHEL code if they can't actually install a system themselves? You could provide the code for the errant library, but to really test it, the developer would probably like to try it on a full RHEL system. And if that is now difficult to do w/o a RHEL subscription, what's the third-party developer to do?
What you'll find is a slow migration away from third-parties supporting RHEL. I'm not sure what the end game here is for IBM, but it makes the entire ecosystem significantly more difficult to work with.