Subject: Re: packages for mac68k
To: Nuno Teixeira <nu@nunotex.freeshell.org>
From: Bryan Vyhmeister <netbsd@bsdjournal.net>
List: port-mac68k
Date: 05/21/2004 00:05:37
I hope all of us can coordinate these ideas into becoming a working
reality. It would be really great to get all of this going.
Bryan
On Tue, May 18, 2004 at 10:12:02PM +0100, Nuno Teixeira wrote:
>
> Hi,
>
> I think your ideas very interesting.
>
> Since I buyed my SE/30, I came to a conclusion: it works! Since that, I
> have already buyed ethernet asante, 128MB ram and a new other SE/30
> just thinking in making a "cluster" myself to build ports. I'm not
> expertized in clusters, but with some help I will make it.
>
> If this project goes forward, I will upgrade my 2 SE/30 with DiiMO 030
> (DOSE3050-FPU) just to power this things up!
>
> I'm having a lot of fun compiling and compiling ports for weeks! Why? It
> works.
>
> I'm on!
>
> Yours,
>
> Nuno Teixeira
>
> On Mon, May 17, 2004 at 03:03:22PM -0700, Bryan Vyhmeister wrote:
> > thelarsons3@cox.net wrote:
> >
> > >I've noticed that binary packages for NetBSD (mac68k in particular) lag
> > >behind the latest released versions for many softwares. Either not
> > >compiled for the latest NetBSD version, or it's an old software version,
> > >or both. Is this package-building process largely automated or does it
> > >require significant manual effort? How does it work? Who/what does it?
> > >I hope this doesn't fall into the RTM/common knowledge realm...I don't
> > >know, and figured other readers of this list might not either.
> >
> > As far as I know, John Klos does the package builds for m68k based
> > systems. Because the fastest m68k based machine is only a 66 MHz 68060,
> > it takes a really long time to build packages. From what I remember, it
> > takes two or three weeks to do a complete package build.
> >
> > There was some discussion a while back about creating some sort of
> > distributed build system to get all of this accomplished more quickly. I
> > am about to setup a cluster of mac68k machines to do package builds. I
> > always want to have the latest packages available myself too.
> >
> > It would be great to get the distributed package build system project
> > back on track. Is anyone still interested?