On Mon, 23 Apr 2012 11:18:40 +0800 [email protected] wrote: > On Mon, 23 Apr 2012 09:12:48 +0700 > Pandu Poluan <[email protected]> wrote: > > > On Apr 23, 2012 1:09 AM, "Volker Armin Hemmann" > > <[email protected]> wrote: > > > > > > Am Sonntag, 22. April 2012, 19:52:16 schrieb Stefan G. Weichinger: > > > > Just browsed the changelog of glibc-2.15: > > > > > > > > http://sourceware.org/ml/libc-alpha/2012-03/msg00836.html > > > > > > > > When I read the NEWS section there with all that "optimized" > > > > stuff I wonder if it makes any sense to rebuild packages here > > > > after upgrading > > glibc? > > > > > > > > > > no, because it is a library. You make use of it anyway. > > > > > > > What about statically linked packages? > > > > Rgds, > > Bless those who keeps on telling people there is no need to rebuild > packages after glibc upgrade, for they must have not used pam or any > other packages that uses dlopen().
To be fair, a complete rebuild of everything is a relatively huge task and usually a waste if done routinely. glibc is never downgraded in any sane system, only upgraded. The glibc ABI and API hardly ever take anything away, just add new stuff. Imagine if glibc behaved like boost wrt API changes <shudder> So leaving everything else intact after upgrading linux-headers and/or glibc gives a system that tends to do exactly what it did before and is in no way broken. Sure, one can rebuild all of world at one's leisure to take advantage of any new features those packages give, but it is not *required* This latest pam nonsense is a very rare event. I really don't feel like doing massive rebuilds routinely to maybe catch rare events... -- Alan McKinnnon [email protected]
