[637] in SIPB_Linux_Development
Re: Source trees.
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Wed Jul 20 08:59:57 1994
Date: Wed, 20 Jul 94 08:59:42 -0400
To: linux-dev@MIT.EDU, netbsd-dev@MIT.EDU
From: Salvatore Valente <svalente@MIT.EDU>
Ok, it's early, I'm tired. My first message was accidentally sent
to the wrong address, and was unclear. Let me try again:
> I think it would be a good idea for linux-dev and netbsd-dev to use
> the same athena source tree.
>
> Somebody should suggest a method for doing this.
> -Sal.
What I mean by "a method" is this:
1) What name are we going to export this as from sipb-nfs?
2) What programs do we want to take from the linux-dev source tree?
From the netbsd-dev source tree? From the Athena 7.7 source tree?
Clearly, any sources that were taken from the linux-athena source tree
and had netbsd support added and nothing taken out should become the
only copy. (That seems to just about always be the case.)
If any netbsd stuff was taken from the UCSC source tree, we should
decide if we want those sources or the linux-dev stuff.
And when Athena 7.7 is publicly released, there are a few programs
that I want to mirror from the 7.7 source tree (in /afs/dev), and
re-port to Linux / NetBSD / whatever. These include:
zephyr: because the linux-athena zephyr sources are a snapshot of the
Athena zephyr sources at a time when they were sort of in flux. As
far as I know, linux-dev hasn't changed anything in the zephyr sources
except xzwrite. (It compiled "out of the box.") So a new snapshot
should be made when it can be made better.
tex: for obvious reasons.
The olc client: because it has readline added.
Anything else that's visibly changed.
That about sums it up for now, and I'm even more tired.
Have a nice day.
-Sal.
