On Saturday 2016-01-23 12:55, SF Markus Elfring wrote:
The problem is that developers just don't do anything about it even if they knew about the existence of these tools.
Are there any more possibilites to reduce unwanted consequences from such situations?
Automatic generation of tags based upon the ABI -- basically the srcmd5 fingerprint approach I suggested.
https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/RPM_Gu...
Those are just freeform strings that serve no purposes with regard to ABI compatibility.
Should RPM capabilities help to manage specific software requirements?
They already do on a daily basis.
How should the available and really usable versions be determined for application programming interfaces which will fit to a selected application binary interface of a needed component?
That is a different category, which does not visibly happen in practice, and which is unrelated to the three bugreports mentioned earlier. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org