They both are a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=903974[https://bugzilla.opensuse.org/show_bug.cgi?id=903974] where I already bemoaned the lack of symbol versions.
Would you like to improve such situations anyhow? Have you got any further ideas to fix similar issues?
Can specific certification marks help to make the reuse of some software packages a bit safer?
Definitely.
Thanks for your acknowledgement.
The dependency *resolution* is fine.
Interesting view …
The problem is with lazy upstream developers who do not update these "marks" *at all* when they made a change.
Do they need any additional and enhanced tools which will make the desired tag (or SONAME) maintenance more convenient and safe?
* Difficulties with activation of another current Nvidia graphic driver https://forums.opensuse.org/showthread.php/512847-Difficulties-with-activati...
The ".run" installer from nvidia is a homebrew solution and tramples on files managed by RPM - which subsequently get replaced by RPM at some point again.
How do you think about the general idea to express the properties "application binary interface" and "application programming interfaces" more often? Would any consistent usage of RPM capabilities help in such use cases? https://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/0.1/html/RPM_Gu... Can they be automatically determined? Which specification style do you prefer at corresponding places? Examples: * gimp(abi) = 4 gimp(api) = 2.0 * php(api) = 20131106 php(zend-abi) = 20131226 php-api = 20131106 php-zend-abi = 20131226 * python(abi) = 2.7 Regards, Markus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org