Re: Future of m68k - Etch and beyond
On Fri, Feb 23, 2007 at 01:03:15PM +0100, Ingo Juergensmann wrote:
> Well, I just had a discussion about m68k and the Etch release.
> My question is now:
> What is the *exact* plan for m68k for Etch and beyond? Was there any action
> yet to ship our own Etch release? Is there the infrastructure in place
> (mirror, ftpadmin, ...)?
I'm sorry; I promised to work on this, but it didn't happen.
> How will the m68k cope with the glibc problem for Lenny in the future?
Good question. We do need the TLS support, and I don't have a clue how
to write it.
> How is the Coldfire port going on?
I made some progress and had a revelation a few weeks back. I have a lot
to learn still, but I'll eventually get there. I hope to be able to make
it work by the time Lenny gets out, but we'll have to see.
It'd be nice if Someone Else(tm) were to help; but if not, I do feel
that I'll be able to complete this by myself.
> Sorry for these questions, but I do feel that Sarge was the last release for
> m68k and the port will die with ending the support for Sarge (1 year after
> Etch release). Without a proper plan for re-joining the release archs I
> don't see any future for the m68k port - very, very sadly - and might act
> appropriatingly therefore (somewhen).
> Ciao... // Fon: 0381-2744150
> Ingo \X/ SIP: email@example.com
> gpg pubkey: http://www.juergensmann.de/ij/public_key.asc
> To UNSUBSCRIBE, email to debian-68k-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22