Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 4/22/2008 7:23 AM: > |> Is it worth writing bootstrap.m4sh, and running it through autom4te to get > |> the shell selection code from autoconf with minimal effort on your part? > |> You'd still probably want to check in the generated bootstrap script, > though. > | > | That's tempting -- and maybe better in a way -- but not enough > | to outweigh the penalty of checking in the generated code. > > But since an installed autoconf is a prerequisite to running bootstrap, > maybe you could document: > > $ git clone ... > $ cd coreutils > $ autom4te --language=m4sh bootstrap.m4sh -o bootstrap > $ ./bootstrap > $ ./configure > $ make > > as the preferred method for getting started, avoiding the need to check in > bootstrap? Or even have a two-level bootstrap: ./bootstrap is a simple > checked-in wrapper which portably calls autom4te on bootstrap_inner.m4sh > then runs bootstrap_inner with the expectation of a better shell?
Actually, I like that. Are you interested in writing the patch? > Oh well, I can dream :) Thanks for persevering. _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
