Sebastian Günther <sam...@guenther-roetgen.de> writes: > First of all the bug is fixed, and a working patch was there 1 day after > the opening. I call this a fast response... > > For ~x86 this is a working solution, and if you use ~x86: b.g.o *is* the > users information system and applying patches should be no problem.
Point taken. > The problem with glibc is, that you only find issues when you recompile > your whole world, which is not needed in most cases. And most of the > errors with glibc-2.10.1 result from wrong castings, which is only a > compile time issue not a run issue. > > And all these problems are upstream, so you can patch for yourself in > gentoo, but the cleaner solution is to wait for upstream to include the > patch there. And release a new version, when they do too... Thanks for your patience and I learned in an earlier thread one very easy way to get things working... I guess you'd still call it a patch... but not requiring setting up your own local portage and producing a patched version. ebuild /usr/portage/<section>/<pkg>/pkg.ebuild configure Do necessary manipulations ebuild /usr/portage/<section>/<pkg>/pkg.ebuild merge I realize in some cases that would be a recurring chore but I kind of doubt it this time. procmail will not likely need updating for some time and then like you've suggested portage will have it fixed.
