User: Password:
|
|
Subscribe / Log in / New account

A proposal for an always-releasable Debian

A proposal for an always-releasable Debian

Posted May 13, 2013 8:30 UTC (Mon) by ovitters (subscriber, #27950)
In reply to: A proposal for an always-releasable Debian by drag
Parent article: A proposal for an always-releasable Debian

We've been doing that for 10+ years?


(Log in to post comments)

A proposal for an always-releasable Debian

Posted May 13, 2013 11:00 UTC (Mon) by nix (subscriber, #2304) [Link]

... and so has everyone else with half a brain releasing shared libraries on Linux.

The problems come when one of the libraries far downstream does, eventually, break its ABI, forcing a cascade of recompilation, or when something you receive has been built against a newer library than you currently have forcing a cascade of updates. Backward-compatibility isn't enough to help there.

A proposal for an always-releasable Debian

Posted May 14, 2013 6:37 UTC (Tue) by muntyan (guest, #58894) [Link]

What about this one: http://www.murrayc.com/permalink/2013/05/07/gtkmm-3-8/?ut...
Hopefully it's not going to become common.

A proposal for an always-releasable Debian

Posted May 14, 2013 14:37 UTC (Tue) by ovitters (subscriber, #27950) [Link]

Good example (unfortunately). Do not see a reply from Matthias (gtk+ maintainer). Loads of replies, but not much why it cannot be avoided. Seems weird.

I do know that sometimes misuse of the API/ABI and library changes can result in breakage. That is not considered too much of a problem (kernel is way stricter in this). This case, I don't have any clue.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds