From: Charles Hedrick (hedrick@athos.rutgers.edu)
Date: 09/27/92


From: hedrick@athos.rutgers.edu (Charles Hedrick)
Subject: Re: Help please: upgrading MCC Interim of some time ago to .97pl4
Date: 28 Sep 1992 03:03:32 GMT

hlu@eecs.wsu.edu (H.J. Lu) writes:

>You can find copies of all the docs about compiler/library on tsx-11 under
>pub/linux/GCC. Any suggestions about better locations?

pub/linux/packages/GCC is fine. I'd say that as long as README points
to everything you need, then you're OK. My concern was your
implication that we had to save a news posting, or the information
would disappear. If you put it into the README, or have README point
to it, then people who missed the posting will still be OK.

Enough people (including me) find the GCC installation confusing that
it might be worth some thought about improving it. One problem is
that GCC is typically broken into files with some ambiguity as to
whether you need them or not. E.g. binutils. Things are even more
interesting in the latest release, with bin4, usrbin4, and usrlib4.
I'd suggest having subdirectories in the release area, probably bin,
src, and other. Bin should include exactly that set of files that you
need to have a complete GCC and library, and installation documents.
As I recall, this includes binutils, libdp, lib41, jump41, inc-4.1,
and 222d7.TZ. Src should include sources and diffs. Other should
include everything else, including bin4, usrbin4, usrlib4. If you
think you're likely to start releasing the libraries and compiler
separately, then I'd suggest separate bin subdirectories, so you can
tell people "I've just updated libc. The compiler hasn't changed, so
you just need the stuff in bin.libc".