Le 18 janv. 2012 à 11:30, Jim Meyering a écrit : > From: Jim Meyering <[email protected]> > > Updating to the latest bootstrap from gnulib involves more of a > change than usual, and updating to the latest gnulib would involve > its own set of challenges with the upcoming quoting changes, so > we update bootstrap manually and separately. > * bootstrap: Update from gnulib. > * Makefile.am: Initialize more variables to empty, so that gnulib.mk > can append to them with "+=". > * bootstrap.conf (gnulib_mk_hook): Remove. No longer honored. > (bootstrap_epilogue): Instead, run the same command, > etc/prefix-gnulib-mk lib/$gnulib_mk, from here. > Temporarily disable "bootstrap_sync=true". > * etc/prefix-gnulib-mk: Don't prepend "lib/" to tokens like -I$(... > or "\".
Looks like hard (and painful) work! What's the coding style for bootstrap etc.? I see some uses of `command`, and some of $(command) (on $AUTOCONF). I definitely prefer the latter, and I also prefer (pattern) in case's cases. Also, I see terribly complex see programs that could be nicer in say Perl. What's the guideline?
