Having to do this is a real pain: $ ./bootstrap-prefix.sh $EPREFIX/tmp make $ ./bootstrap-prefix.sh $EPREFIX/tmp wget $ ./bootstrap-prefix.sh $EPREFIX/tmp sed $ ./bootstrap-prefix.sh $EPREFIX/tmp python $ ./bootstrap-prefix.sh $EPREFIX/tmp coreutils6 $ ./bootstrap-prefix.sh $EPREFIX/tmp findutils $ ./bootstrap-prefix.sh $EPREFIX/tmp tar15 $ ./bootstrap-prefix.sh $EPREFIX/tmp patch9 $ ./bootstrap-prefix.sh $EPREFIX/tmp grep $ ./bootstrap-prefix.sh $EPREFIX/tmp gawk $ ./bootstrap-prefix.sh $EPREFIX/tmp bash being able to do this instead would be more simple: $ ./bootstrap-prefix.sh $EPREFIX/tmp make wget sed python coreutils6 findutils tar15 patch9 grep gawk bash
Created attachment 259211 [details, diff] Patch v1
v1 is not ideal, there is no error checking if a build fails. Historically, we have avoided this because the bootstrap guides are meant to be hands on, very similar to the Gentoo Linux handbooks, which allows the user to "get to know" Gentoo Prefix. Also, same reason why we don't do "emerge A B C" later in the docs...
Feel free to reopen if you want to pursue this.