**** BEGIN LOGGING AT Thu Sep 01 02:59:58 2016
Sep 01 14:34:50 <pabs3> http://cascardo.info/blog/GNU_libc_and_Linux/
Sep 01 14:45:50 <bencoh> sp trie "_
Sep 01 14:46:00 <bencoh> so true :)
Sep 01 19:14:20 <DocScrutinizer05> indeed
Sep 01 19:16:04 <DocScrutinizer05> this however is also a problem of (glibc et al) devels and maintainers who should use as old as possible (maybe security patched) versions of all libs
Sep 01 19:17:38 <DocScrutinizer05> while a new lib is generally supposed to be a compatible superset of its ancestor, obviously an old lib can't provide compatibility for programs built against a newer version
Sep 01 19:21:58 <DocScrutinizer05> which means any program built against an old lib should work under a newer version of same lib, while the other way around it obviously won't work. As long as devels do not *absolutely* need new functions in a lib not available from older versions of same lib, they should build against the older version, even when it's maybe encumbered by security issues. Those issues will have a fix in any newer lib the binary will run on, as 
Sep 01 19:21:59 <DocScrutinizer05> long as lib ABI compatibility is preserved
**** ENDING LOGGING AT Fri Sep 02 02:59:58 2016