[490] in NetBSD-Development
Re: login and login.krb changes
daemon@ATHENA.MIT.EDU (John Hawkinson)
Fri Jan 27 14:02:12 1995
Date: Fri, 27 Jan 1995 13:59:56 -0500
To: Greg Hudson <ghudson@MIT.EDU>
Cc: John Hawkinson <jhawk@MIT.EDU>, netbsd-dev@MIT.EDU
In-Reply-To: "[485] in NetBSD-Development"
From: John Hawkinson <jhawk@MIT.EDU>
>
> > 2) Makefile.netbsd with an @sys symlink from Makefile. Notice
> > this is a 44BSD Makefile.
>
> I would hardly call this a "paragon" of a way a source tree ought to
> be set up.
I think I was having foot-in-mouth disease induced by lack of sleep.
This has not yet been corrected, so I'd best be careful.
> Having a separate Makefile for each platform we port to is generally
> the wrong answer, since it institutionalizes the notion that we
> should spend lots of effort porting to each platform that we want.
Perhaps. Since there was no Makefile before, and generation was
trivial, I chose to do it this way. If the Linux people would care
to make it work under Linux (it shouldn't be difficult given the
linux port of pmake), then it'd be portable.
> particular operating system. That is to say, imake, configure, and
> vanilla Make are okay (except that imake sucks), whereas BSD 4.4 make
> is not okay, since it will be completely useless to us on any other
> platform.
pmake is in outland for Linux, and most other platforms (thanks, Sal!).
> We should also try to avoid "#ifdef __NetBSD__" when porting code,
Sorry, I was _NOT_ referring to the quality of the changes. I was referrring
to the RCS structure. I haven't gone through the changes yet (I just imported Yoav's; I thought this rcs log entry was clear:
revision 1.71.1.1
date: 1995/01/27 11:12:16; author: jhawk; state: Exp; lines: +192 -192
Fixed RCS branching to be consistant w/ Athena.
Previous branch read:
:revision 1.2
:date: 1995/01/27 08:23:44; author: yoav; state: Exp; lines: +165 -41
:Fixes for netbsd
:----------------------------
:revision 1.1
:date: 1995/01/05 04:20:29; author: yoav; state: Exp;
:Initial revision
----------------------------
), though I'm planning on doing so before merging in Craig's latest and
remitting stuff back to him.
--jhawk
