[2027] in SIPB_Linux_Development
Re: How about a new RH-A release for next year?
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jun 1 17:47:14 1998
To: Derek Atkins <warlord@MIT.EDU>
Cc: amu@MIT.EDU (Aaron M. Ucko), Emil Sit <sit@MIT.EDU>, linux-dev@MIT.EDU
In-Reply-To: Your message of "01 Jun 1998 10:21:09 EDT."
<sjmlnrhmcdm.fsf@squeamish-ossifrage.arepa.com>
Date: Mon, 01 Jun 1998 17:46:56 EDT
From: Greg Hudson <ghudson@MIT.EDU>
> It will take some time to do the port, but a coordinated effort can
> quickly run through the tree. I'd recommend you make a file
> containing all the packages, and as someone tries to port a
> particular package you mark your name in the file. Then mark it as
> "done" when you check-in working code.
Please make sure to go read doc/procedures and doc/sipb and go through
sipb-source-reviewers. I encourage people to read the rest of doc/*
as well, but those two are the important parts.
Sal already submitted and checked in patches for pretty much all of
athena/* and third/*, so I suspect you'll find that most everything
will just build. (Assuming you can figure out the build system, of
course. :) You may find the self-contained building feature useful
for coping with dependencies.)
> For auto-updates I think you'd need to install all of Linux into a
> locker somewhere (/os) so you can update from it. Either that or
> automate the update.pl script.
Just for the sake of consistency, the current trend on Athena
platforms would put Red Hat RPMs into /install. /os has always been a
reference filesystem and sometimes a target of symlinks (in Solaris
and IRIX). Athena RPMs don't have any precedent on other ports, but I
would tend towards putting those into /install along with the Red Hat
RPMs, possibly separated off into another directory.
