Andrew Haley (aph@xxxxxxxxxx) said: > > and, most importantly, because it is NOT our job to work around bugs > > in proprietary software! > > How is any of that a reason not to patch glibc? > > Upside of patching: happy users. > Downside: nothing. Downside: cranky libc maintainers While possibly sometimes hard to distinguish from the default state, I'm guessing that the chance of getting glibc upstream to change their behavior for a closed-source app that broke semantics defined in K&R is nil, and they're going to be pretty annoyed if we slam that in on top of them. Bill -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
