i dont remember how glibc handled their last breakage, i assume not well
we need to start shaming old distros
-
rose
- Posts: 55
- Joined: Tue Aug 26, 2025 9:08 pm
- Location: My wifes arms ^^
- Pronouns: she/her
- Fediverse: https://social.pinkro.se/users/rose
- XMPP: rose@chat.pinkro.se
- Contact:
Re: we need to start shaming old distros
Yep 100%
i dont remember how glibc handled their last breakage, i assume not well
i dont remember how glibc handled their last breakage, i assume not well
-
np93
- Posts: 26
- Joined: Tue Aug 26, 2025 7:23 pm
- Location: neptune
- Pronouns: she/they/it
- Fediverse: https://zoner.work/@ada
- Contact:
Re: we need to start shaming old distros
(and cost)lizzy wrote: Thu Aug 28, 2025 3:18 pm I agree, it's also a matter of attitude.
QA is for preventing breakage ahead of time, but even if you don't have QA you should still be treating regressions that break someone's use case as serious bugs to be fixed.
-
navi
- Site Admin
- Posts: 8
- Joined: Tue Aug 26, 2025 9:10 pm
- Location: s-23 sierpinski
- Pronouns: she/her
- Fediverse: https://social.vlhl.dev/navi
- Matrix: @navi:vlhl.dev
- XMPP: xmpp://navi@vlhl.dev
- Contact:
Re: we need to start shaming old distros
glibc tries a lot to not break abi at least, they're the major user of versioned symbols, keeping old implementation around forever basically -- but i guess that started after one-too-many breakagesrose wrote: Thu Aug 28, 2025 3:15 pm of course, but projects like glibc not doing proper QA at times and doing random ABI changes that break everything can't really be excused with "its just hobbyists" imo
(versioned symbols are useful even without keeping old versions around, since they allow clear errors like "this binary needs libnya.so.2.15 for symbol nya_foo, but only libnya.so.2.10 is available")
