Subject: Differences between 1.2 tarballs and now
To: None <mrg@eterna.com.au>
From: Greg Earle <earle@isolar.Tujunga.CA.US>
List: port-sparc
Date: 09/24/1996 00:58:43
>>> ftp.netbsd.org:/pub/NetBSD/NetBSD-1.2/sparc has the 1.2 sets for the sparc
>> 
>>    src/distrib/...
> 
> This directory is for building releases.

Fair enough ...

>>    src/domestic/...
> 
> There don't appear to be secr sets for the SPARC this time.  Probably
> because pk isn't allow to have the code.  :-)

This is kinda too bad.  Is there anything we can do about this?  I'm sure
some U.S. folks would like to get /usr/include/kerberosIV and the domestic
libtelnet et al. from unbundling a "secr.tar.gz" file ...

> So, the problem is that the send-pr in the sparc 1.2 release will have
> 1.2_BETA.  pk, perhaps you should fix this.  :-)

Yup.  Quick n' dirty:

netbsd4me:1:52 % diff -rc0 ./usr/bin/send-pr /usr/bin/send-pr
*** ./usr/bin/send-pr   Sat Aug 24 08:51:32 1996
--- /usr/bin/send-pr    Fri Sep 13 05:57:11 1996
***************
*** 44 ****
! DEFAULT_RELEASE="1.2_BETA"
--- 44 ----
! DEFAULT_RELEASE="1.2"

> Oh, sys/param.h may not be up to date in the installed includes.

Yup again:

*** ./usr/include/sys/param.h	Tue Jul  2 09:14:45 1996
--- /usr/include/sys/param.h	Thu Sep 12 00:34:33 1996
***************
*** 1 ****
! /*	$NetBSD: param.h,v 1.23.4.2 1996/06/25 01:40:43 jtc Exp $	*/
--- 1 ----
! /*	$NetBSD: param.h,v 1.23.4.3 1996/09/10 19:51:11 jtc Exp $	*/
***************
*** 47 ****
! #define NetBSD	199606		/* NetBSD version (year & month). */
--- 47 ----
! #define NetBSD	199609		/* NetBSD version (year & month). */

One thing I just noticed: the comp.tar.gz tarball doesn't contain a copy of
<machine/conf.h> (which is a copy of /usr/src/sys/arch/sparc/include/conf.h).
I did a comparison between the include tree built from comp.tar.gz and my own,
and (in addition to the missing ./usr/include/kerberosIV) I had noticed

	Only in /usr/include/machine: conf.h

Since my "make build" installed this at some point, I was curious as to why
it's not in the comp.tar.gz tarball.   (Doesn't seem like a big deal, but
when you see a singularity like that ... )

	- Greg