Terry Barnaby wrote:
> Well in this case I have created a suitable compat lib, all I did was
> re-introduce the bits to the SPEC file that removed the building of the
> compat lib and we are fine. I haven't separated it out from the main
> ncurses SPEC through and have only done this locally as I have no
> knowledge of the hoops to create a separate package and that seems like
> the wrong way to do this in general. I have made this available to
> others who will be in the same boat.
Typically, compatibility libraries should not be subpackages of the main
library. But ncurses is a bit peculiar in that, as I understand it, the
latest code can still be built with the old ABI. So in that case, it at
least makes sense to build both from the same SRPM. But only if they are
going to be maintained by the same maintainer(s), i.e., you should probably
sign up as a comaintainer for ncurses in Fedora if you want to do it that
way. And of course only as long as upstream continues supporting building
for the old ABI. If they drop support, then a separate compatibility package
with an old version that supports the old ABI will be needed.
Kevin Kofler
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
