On Mon, Jun 19, 2006 at 01:33:50AM +0200, Aurélien GÉRÔME wrote: > I think you are all aware the m68k port can be dropped for etch > if nothing is done to speed up m68k buildd network at least, but > unfortunately, not at last. Though, I do not know for sure whether > we still need kernels 2.2 and 2.4 for m68k: kernel 2.6 works well on > my Quadra950 and on a friend's Quadra940AV. However, it seems there > is some toolchain work needed from what I read on that list. The 2.2 and 2.4 kernels are going to be dropped from etch -- spend the time on 2.6. Amiga is mostly ready for primetime. Mac mostly isn't. None of the other subarchs work at all as far as I know. So we'll move forward based on amiga and maybe mac. I hope to keep everything installing with d-i, but moving everything to 2.6 is the only long term strategy. What exactly did you do to get the 950's working? I'd love to upgrade my buildds. Whether or not m68k is a release candidate for etch depends largely on whether or not we can get caught up and stay caught up. Apparently that means we need more fast buildds and more porters. We can certainly use people willing to work on the toolchain (we've had bugs open for years), but perhaps even more important is that we need someone (or better, several people) managing the bugs for m68k gcc and upstream. This means filing good bug reports, checking against various compiler versions, and if you can program in c, maybe reducing test cases, but really that's not as important. Management and knowing the score with gcc is the key. Right now, that's killing us faster than anything else. Darn, I'm ranting again. ;-) -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net>
Attachment:
signature.asc
Description: Digital signature