Re: [gentoo-alt] Allow non-interactive bootstrap to be stopped at arbitrary stages

[Benda Xu]

Hi Sam,

Sam Pfeiffer <sammypfeiffer@×××××.com> writes:

> First, thanks for explaining your proposal in a detailed way. I
> sincerely didn't understand exactly what you meant.
>
> Let me explain further. I found "complicated" to know what environment
> variables I needed to set manually in order to make use of the
> bootstrap script calling it in the way you just presented. I did
> attempt to do it previously and failed miserably.  When looking at the
> bootstrap-prefix.sh script there are a lot of variables in a 3000+
> lines script, it's kind of daunting.  And when your goal is "I just
> need this to bootstrap, and it looks very complicated" you want to the
> most automated way (someone smart wrote the automated way!).
>
> Now I understood what do I need to set up.
> In hindsight, it was pretty obvious, as the interactive script itself spits out for me:
> EPREFIX=/tmp/gentoo
> CHOST=x86_64-pc-linux-gnu
> PATH=/tmp/gentoo/usr/bin:/tmp/gentoo/bin:/tmp/gentoo/tmp/usr/bin:/tmp/gentoo/tmp/bin:/tmp/gentoo/tmp/usr/local/bin:/usr/bin:/bin
> MAKEOPTS=-j5

You can cross out CHOST and MAKEOPTS.  Do you think setting EPREFIX and
PATH a complex task to do?

The "same codepath" you mentioned just sets these 4 variables.


I don't like this patch for extreme reproducibility.  But that's only my
personal opinion.  You can keep your version of bootstrap script for
your purpose or approach grobian for an alternative review.

> [...]

> Meanwhile using the same codepath we are already using "guarantees" I
> don't need to fight any of that. Neither me, you or the next
> maintainer. To me, the mental model I need to create and maintain in
> my head from the version I'm proposing is tinier than from the one
> where I need to figure out the environment variables and also
> copy-paste the MAKEOPTS guesswork.

I am very surprised that you need copy-paste and guesswork for the 4
variables.

> [...]

Yours,
Benda