Re:CVE-2015-8126: Multiple buffer overflows in libpng
by hyperion2010 on Saturday November 14, 2015 @06:15PM
(#10567717)
Oh man, the number of times I have delayed updating a system because different programs required different versions of libpng. On the other hand, having used gentoo as my primary distro for nearly a decade I have found that there are some serious benefits to actually knowing what libs are actually involved in creating a functional linux environment.
Re:CVE-2015-8126: Multiple buffer overflows in libpng
by noobermin on Saturday November 14, 2015 @04:22PM
(#10567314)
No that's exactly right. I'm specifically referring to your [0] comment. It allows me to spread the compilation over a longer time (days) while being able to use the old things without breakage. Before, I had to recompile everything and things would be unworkable until everything was recompiled. I now have a number of boxes with distcc so compilation times aren't that bad nowadays. But back in 2010 or so, when I just had a shitty gateway laptop, dealing with libpng version bumps was a weekend affair.
Re:CVE-2015-8126: Multiple buffer overflows in libpng
by simoncion on Saturday November 14, 2015 @04:25PM
(#10567327)
> Before, I had to recompile everything and things would be unworkable until everything was recompiled.
Oh god, tell me about it. I was around for the first libpng upgrade catastrophe, way back when. Portage/emerge has gotten so much better since then. :D
I'm also a Gentoo user. (Hi! :D )
ISTR that preserved-libs "just" lets you delay recompilation of affected packages [0] by keeping the old libs around until everything that needs rebuilding to link against the new version has been rebuilt. You still need to rebuild packages. Am I wrong about that?
[0] Or, -alternatively- "just" lets you keep your system working while you rebuild affected packages.