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

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

 



On Sun, Jul 04, 2021 at 07:11:14AM -0500, Richard Shaw wrote:
> On Thu, Jul 1, 2021 at 1:52 PM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>     https://akkadia.org/drepper/dsohowto.pdf
> 
>     as well as:
> 
>     https://gcc.gnu.org/wiki/SymbolVersioning
> 
> 
> Is that something that can be easily implemented at the packager level?

Unfortunately not, except in the sense that if upstream are doing it
right then RPM packaging will automatically do the right thing too.

Also I think I claimed this was possible/easy for C++ and IIRC there
are problems which make it difficult with C++.  It's certainly much
easier if you have a plain C API.

> Also, in the case of OpenEXR upstream (ASWF) has reorganized the
> libraries over the last couple of releases[1], merging some and
> splitting out others creating a real mess. In fact, one of the other
> ASWF projects, OpenVDB isn't even compatible with OpenEXR 3 and
> won't be until the next major release. 

It sounds like they're not really taking the whole backwards
compatibility thing seriously.

> So is my only real option to create a compat package and migrate all the
> projects that can't use OpenEXR 3 to it? 

I think so :-(

Rich.

> For posterity here's my working COPR with the fairly long list of dependencies:
> 
> https://copr.fedorainfracloud.org/coprs/hobbes1069/openexr/builds/
> 
> Thanks,
> Richard 
> 
> [1] https://github.com/AcademySoftwareFoundation/Imath/blob/master/docs/
> PortingGuide2-3.md

> _______________________________________________
> 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


-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
_______________________________________________
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