Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?

Liste des GroupesRevenir à cubf misc 
Sujet : Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?
De : johnl (at) *nospam* taugh.com (John Levine)
Groupes : comp.unix.bsd.freebsd.misc
Date : 19. Oct 2024, 21:49:10
Autres entêtes
Organisation : Taughannock Networks
Message-ID : <vf1606$2v1o$1@gal.iecc.com>
References : 1
User-Agent : trn 4.0-test77 (Sep 1, 2010)
It appears that Robin Haberkorn  <robin.haberkorn@googlemail.com> said:
applications, even those that link only against plain C libraries. It's
rare, but you can't exclude that some minor library release breaks the API
- ABI is of course not a problem in C, compared to C++.

The difference between a minor and major version is that minor versions have
the same interfaces.  If the interfaces change, thaat's a major version.

It sounds like the bug is that a breaking change was shipped as a minor version
rather than a major one.

--
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

Date Sujet#  Auteur
19 Oct 24 * [ports] Shouldn't we rebuild all dependant packages whenever a library changes?3Robin Haberkorn
19 Oct 24 `* Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?2John Levine
21 Oct 24  `- Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?1Robin Haberkorn

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal