I recently had a hard disk failure and needed to reinstall everything on my system. I generally have used mm-sources in the past. However, I have had intermitent problems with the 2.6.8.1 releases and feel that the release canidates for 2.6.9 are too risky, especially after the corruption problems with the first RC. However, everything before 2.6.8.1 has been removed from the portage with no explanation as to why. I am not saying we need to keep ebuilds for every 2.6 release in the last year. I can go and download and install the mm patch set for the 2.6.7 kernel, which was the last problem free release for me, but that is not a good solution since the whole advantage of portage is not having to do that in the first place. I propose that the current pruning be kept for mm-sources, except for the last (mm-sources-2.6.8.1-r4 should be kept if there are no more releases before 2.6.9 are released) ebuild for at least the the prior 4 final releases remain in the portage tree. I have noted that devleopment-sources and gentoo-dev-sources have e-builds all the way back to the 2.6.1 release. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Running mm-sources is fairly risky stuff and should only really be used by people wanting/needing to test the very latest code. For that reason, theres not much point keeping old versions around. I'd suggest that you run gentoo-dev-sources. If the current stable version is unstable but a fix has been merged upstream, just point out the problem and fix to me and I'll consider including it in our patchset.
