the setrlimit changes in glibc 2.1.3

Roland McGrath roland@frob.com
Thu Jan 13 11:40:00 GMT 2000


So I think the real question here is, what warranted this kind of change in
a "bug-fix" release?  I think folks around here have gotten pretty unclear
on the concept of maintenance releases, and everybody's playing fast and loose.
This is just not the way to operate.  That's why we have a development
branch, for pete's sake.  Are we going to have to add another level of ".x"
to the versions to get a truly conservative maintenance release branch?

And, Mark: I'm afraid the realities of packaging systems (and of humans)
make it hopelessly unwise to attempt to have "the right thing" for anyone
be to upgrade their shared libraries differently than they upgrade their
development environment.


More information about the Libc-hacker mailing list