Well, the next question to answer is, should the package without active upstream maintenance be the reason for slowing down the progress of another project? Should such a package remain in Fedora at all?

I would personally avoid to do such openexr2 package split, just because I know how painful it will become to get rid of such versions later from Fedora and do it just as transition never worked for me - it remained in the compose for much longer than expected, but it's just my 0.02$.

Best regards

Josef Ridky
Senior Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

On Mon, Jun 7, 2021 at 6:20 PM Richard Shaw <hobbes1069@gmail.com> wrote:

I've been able to update several packages to build with OpenEXR 3 but there are many more to go, perhaps too many for me to handle.

Specifically (and ironically) OpenVDB which is also a project under the stewardship of the ASWF has not had a single commit to it to be compatible with OpenEXR 3.

For that reason I'm considering submitting for an openexr2 package. But that means really mapping out the dependency chain, right? We don't want both packages used within the same "stack".

Thoughts?

Thanks,
Richard
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure