RE: Installing Arusha on a new site (long, but dull)

Will Partain writes:
> Are you going to be able to do "virgin installs" for a few
> days longer (i.e. after I get some patches in)?

Yes.  I will continue to expand our Arusha configuration and will repeat
virgin installs.  Eventually I need to perform virgin installs on a few
isolated internal production networks so I want to be sure the process
works.

> Here's a proposed solution -- you guys yell, OK?  I will use
> the C compiler (host field <CC>) as an example.
> ...
> * Yes, it's turgid (but straightforward).  Special pleading
>   could then be removed from all individual packages.

It looks like it will work, so turgid is ok.

Can this logic be captured in a shell function somewhere?  Most of the basic
packages (gcc, tar, md5sum, ...) appear in multiple ALL.xml package methods.
For example, md5sum is used by verify-source, create-manifest, and verify.
Three copies of the same turgid code will tend to diverge over time.

[A sample divergence:  Sidai packages ark-prereq-utils, binutils, gcc, and
gzip set parameter MD5SUM to @proxy-host:MD5SUM-BOOT.  Packages texinfo and
texutils set the same parameter to @proxy-host:MD5SUM_BOOT.]

Joel