[1907] in Kerberos_V5_Development
Re: binary distributions of krb5 1.0?
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Oct 30 14:38:48 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: krbdev@MIT.EDU
From: Ken Raeburn <raeburn@cygnus.com>
Date: 30 Oct 1996 14:36:47 -0500
In-Reply-To: "Barry Jaspan"'s message of Wed, 30 Oct 1996 12:44:29 -0500
"Barry Jaspan" <bjaspan@MIT.EDU> writes:
> o Disk space on athena-dist. If our binary distributions only
> contained gzip'ed tar files containing headers, libraries, and
> stripped executables, without .o files and without debugging
> information, how much space would it really require? Perhaps not all
> that much. Also, perhaps we can arrange for another site to provide
> the binary distribution space.
Here's the sizes for our binary distributions to our customers. These
include stuff that the MIT version wouldn't.
3320 -rw-rw-r-- 2 raeburn cygnus 3388681 Sep 18 19:40 alpha-dec-osf3.2-kerbnet-bin.tgz
2496 -rw-rw-r-- 5 raeburn cygnus 2544177 Sep 18 19:40 hppa1.1-hp-hpux10.01-kerbnet-bin.tgz
3096 -rw-rw-r-- 6 raeburn cygnus 3156327 Sep 18 19:41 hppa1.1-hp-hpux9.04-kerbnet-bin.tgz
1936 -rw-rw-r-- 4 raeburn cygnus 1972949 Sep 18 19:41 i586-unknown-linux-kerbnet-bin.tgz
3256 -rw-rw-r-- 8 raeburn cygnus 3325237 Sep 18 19:41 mips-sgi-irix5.3-kerbnet-bin.tgz
1400 -rw-rw-r-- 4 raeburn cygnus 1418953 Sep 18 19:42 powerpc-ibm-aix4.1.4.0-kerbnet-bin.tgz
1544 -rw-rw-r-- 3 raeburn cygnus 1564929 Sep 18 19:42 rs6000-ibm-aix3.2.5-kerbnet-bin.tgz
2088 -rw-rw-r-- 14 raeburn cygnus 2122383 Sep 18 19:52 sparc-sun-solaris2.4-kerbnet-bin.tgz
1904 -rw-rw-r-- 12 raeburn cygnus 1933766 Sep 18 19:42 sparc-sun-sunos4.1.4-kerbnet-bin.tgz
> o Extra effort at release time. Not really. We should compile every
> release we make on every platform we have access to as a regular
> matter of release testing. Then, we can just tar up that final test
> build tree (or, rather, the result of "make install") as the binary
> distribution. Our initial binary distribution set only has to include
> those platforms we have access to; we can later accept compiled
> distributions from other highly-trusted sources (of which there may be
> none) if we wish.
We use a build script which makes the
autoconf/configure/compile/test/build tgz file sequence a one-line
command. The extra effort is minimal.
I agree this would be a good idea, especially for the non-Unix
systems.
