| Deutsch English Français Italiano |
|
<vf1606$2v1o$1@gal.iecc.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.iecc.com!.POSTED.news.iecc.com!not-for-mail From: John Levine <johnl@taugh.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes? Date: Sat, 19 Oct 2024 20:49:10 -0000 (UTC) Organization: Taughannock Networks Message-ID: <vf1606$2v1o$1@gal.iecc.com> References: <8a5d1c33-906e-f61d-d39a-ad5a560fc24f@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 19 Oct 2024 20:49:10 -0000 (UTC) Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="97336"; mail-complaints-to="abuse@iecc.com" In-Reply-To: <8a5d1c33-906e-f61d-d39a-ad5a560fc24f@googlemail.com> Cleverness: some X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: johnl@iecc.com (John Levine) Bytes: 1666 Lines: 14 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