[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pure64 port visibility

On Mon, May 24, 2004 at 03:08:20AM -0500, Chris Cheney wrote:
> On Sun, May 23, 2004 at 10:39:42PM -0500, John Goerzen wrote:
> > On Sun, May 23, 2004 at 10:33:18PM +0200, Frederik Schueler wrote:
> > > In order for the pure64 port to be more visible, I opt for the following
> > > thinks to be done by someone who actually has the permissions for it:
> > > 
> > > 1. set the development status of the alioth project to either "Mature"
> > >    or "Production/Stable".
> > 
> > I don't think this is really accurate.
> What milestones do you think we still have to reach before getting to
> that point? I am not saying it should be considered "Mature" but I was
> just wondering what you think we should base our decision on.

Being mostly compiled and being well-tested and working are different
things :-)

Before I'd consider a port mature, I'd expect it to have been part of
the official Debian infrastructure, and have a working installation
procedure, for some time, so that many people are trying it out.  I'd
also expect there to be no showstopper bugs for some time in basic
system services -- dpkg, libc, x, apt, etc.

While our port has probably progressed at a more rapid rate than any
other in Debian since the introduction of pure64, still it has not been
around very long and has not had many eyeballs looking at it yet.

> 1. We are at 93.5% compiled (most remaining packages have FTBFS RC bugs)
> 2. We have a working debian-installer image (I think?)
> 3. ...
> The only major roadblock that I currently know of is the lack of a
> working native 64bit bootloader.

GRUB does work to boot amd64 kernels, and I would suspect lilo does too.
Of course, the question really may be finding installers for those two
that run in 64-bit mode.

One trick I used on DFS is I provided the grub package on the i386 CD.
amd64 users can copy the relevant files into /boot/grub, then reboot,
and use the grub installation on the CD to finish the installation on
their HD.  That, of course, is not really sufficient for a production
system but it's something.

-- John

Reply to: