"Rick \"Zero_Chaos\" Farina" <zeroch...@gentoo.org> writes:
> While I'm not nearly good enough to detail how this should happen > exactly, please, may I beg, do an eclass revision for this. There is an r1 candidate as Paweł initiated (bug 474358) > The fact that this hasn't been done clearly implies it is a lot of > work. Let's not risk stable, let's simply make toolchain-r1.eclass or > whatever, and bump that to eapi5. At the end of the day, this allows > working and testing without odd issues, and if everyone really hates > that idea you can simply drop the changes into the original eclass > when it's all done. Having a unstable eclass as toolchain-r1.eclass in tree might not be a good idea compared to an overlay though. Regarding eclass, I have a question: Why do we keep all old versions of gcc and glibc? If the point is only being upgradable from old Gentoo, is the requirement lefted now? If it is for users who need a specific version of gcc/glibc, why don't we create a toolchain-archive overlay for that purpose? In the overlay we can have historical snapshots of toolchain.eclass, too. Keeping only a few version of gcc in tree will ease the maintenance of toolchain eclass a lot. Benda
