Mailinglist Archive: opensuse-packaging (129 mails)

< Previous Next >
Re: [opensuse-packaging] Extensions for specification of application binary/programming interfaces?
  • From: "SF Markus Elfring" <elfring@xxxxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 22 Jan 2016 20:46:51 +0100
  • Message-id: <trinity-c94fe449-30e0-4a0d-852b-105093a15129-1453492011376@3capp-webde-bap21>
I suggest you cut the salesbabble, and come up with a *concrete* case
where the existing RPM mechanisms are insufficient, instead of making
up hypothetical blurry scenarios involving some unspecified packages
and interfaces.

How do you think about to make the combination of the properties
"application binary interface" and "application programming interface"
safer for software libraries like the following?

* libmodman1 / libproxy1
https://bugzilla.opensuse.org/show_bug.cgi?id=937157#c5

* yast2-core / libyui6
https://bugzilla.suse.com/show_bug.cgi?id=937665#c2

* Difficulties with activation of another current Nvidia graphic driver

https://forums.opensuse.org/showthread.php/512847-Difficulties-with-activation-of-another-current-Nvidia-graphic-driver


Can specific certification marks help to make the reuse of some software
packages a bit safer?

Would you like to improve dependency resolution a bit more?

Regards,
Markus
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups