what should bootstrap *really* do?

[Hans-Peter Nilsson]

> From: Alexandre Oliva <aoliva@redhat.com>
> Date: 14 Nov 2000 16:16:17 -0200

> On Nov 14, 2000, Hans-Peter Nilsson <hans-peter.nilsson@axis.com> wrote:
> > Ok, bad name.  Not a native speaker and so on.
> > Perhaps bootstrap-continue?
> 
> I already find it bad enough that the default rule is not the one we
> recommend for users.  IMHO, adding more complexity to that is a bad
> idea.  I'd rather keep `bootstrap' simple for end users (i.e., have it
> proceed from the point in which it stopped, for whatever reason) and
> create alternate rules for developers.

I share the opinion that "bootstrap" should do from scratch and
be what is used by end users, while other targets, like
bootstrap-whatever, is for developers.  Anything other than nil
as the initial state for end-users running bootstrap is adding
trouble.

Imagine: `So your installation failed.  How many times did you
write "make bootstrap" and what were the messages at the points
of failure and the reasons?'

brgds, H-P