Re: libfoo.$major requirements/guidelines

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

 



On Mon, Aug 19, 2019 at 7:33 PM Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote:
>
> >>>>> "BJM" == Brian J Murrell <brian@xxxxxxxxxxxxxxx> writes:
>
> BJM> How can you replace libfoo-1.00 with libfoo-2.0.0 when some
> BJM> software has not updated to libfoo-2.0.0's ABI breaking changes
> BJM> yet?
>
> Create a libfoo1 package, have it include the necessary library files
> (and perhaps a -devel subpackage if you wish for things to compile
> against it) and update the base libfoo package to the new version.
>
> We do this all the time.  Some packages utilize an older naming scheme
> involving a "compat-" prefix but that shouldn't be used these days.

We also strive to maintain ABI stability on stable releases, so in theory
this happens during major upgrades when compat packages are not
involved.

Dridi
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-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/packaging@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux