Re: How to (better) deal with library major API changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 1, 2021 at 12:35 PM Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote:
<top post>

Or, if I may be so bold—

Convince the developers to use versioned symbols when they break the API/ABI.

This is the 21st Century, and we have solutions for this. It's not rocket surgery.

</top post>

That's actually not a problem most of the time. Some upstreams even unnecessarily bump their soversion. But maintaining two (or potentially more) versions of a library does create significant extra work for the packager.  One example is the Coin package, currently Coin2/Coin3/Coin4 with all the alternatives gunk.

Thanks,
Richard
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux