Now, the security policies, includes that we should not have packages affected from security bugs in the tree. If you want to keep old glibc, please mask them.
it's already not possible to downgrade glibc -- the ebuild itself will abort. so removing/masking "solves" a problem that doesn't exist.
(In reply to SpanKY from comment #1) > it's already not possible to downgrade glibc -- the ebuild itself will > abort. so removing/masking "solves" a problem that doesn't exist. So for which purpose they are in the tree?
(In reply to Agostino Sarubbo from comment #2) cross-compilers mostly. we also have older ones for people who can't upgrade to linux-2.6.16 or newer. over time we already migrate things from the main tree to the toolchain overlay, but i see no reason to accelerate the natural course of things for a non-issue.