Add "autoreconf" recipe command

[Chandler Carruth <chandlerc@…>]

To allow easy building of GNU Autotools packages, provide a command to directly call autoreconf and generate all necessary files for configure and make. Proposed syntax as follows:

<c:autoreconf install="1" force="1" symlink="1">

With only install defaulting to 1. It should generate the following:

# autoreconf --install --force --symlink

[Chandler Carruth <chandlerc@…>]

Further information about autoreconf, snipped from its help:

Usage: /usr/bin/autoreconf-2.59 [OPTION] ... [CONFIGURE-AC or DIRECTORY] ...

Run `autoconf' (and `autoheader', `aclocal', `automake', `autopoint'
(formerly `gettextize'), and `libtoolize' where appropriate)
repeatedly to remake the GNU Build System files in the DIRECTORIES or
the directory trees driven by CONFIGURE-AC (defaulting to `.').

<snip>

Operation modes:
  -h, --help               print this help, then exit
  -V, --version            print version number, then exit
  -v, --verbose            verbosely report processing
  -d, --debug              don't remove temporary files
  -f, --force              consider all files obsolete
  -i, --install            copy missing auxiliary files
  -s, --symlink            with -i, install symbolic links instead of copies
  -m, --make               when applicable, re-run ./configure && make
  -W, --warnings=CATEGORY  report the warnings falling in CATEGORY [syntax]

Warning categories include:
  `cross'         cross compilation issues
  `gnu'           GNU coding standards (default in gnu and gnits modes)
  `obsolete'      obsolete features or constructions
  `override'      user redefinitions of Automake rules or variables
  `portability'   portability issues
  `syntax'        dubious syntactic constructs (default)
  `unsupported'   unsupported or incomplete features (default)
  `all'           all the warnings
  `no-CATEGORY'   turn off warnings in CATEGORY
  `none'          turn off all the warnings
  `error'         treat warnings as errors

The environment variable `WARNINGS' is honored.  Some subtools might
support other warning types, using `all' is encouraged.

<snip>

Library directories:
  -B, --prepend-include=DIR  prepend directory DIR to search path
  -I, --include=DIR          append directory DIR to search path

Of these various flags the ones i think are relevant are:

• force -- allow overriding existing files in repository (some people do this...)
• install -- necessary for many projects to successfully run
• symlink -- people may prefer symlinking when installing, especially temporarily...
• warnings -- different packages may want builds to fail at different levels, or need this information
• prepend-include -- may be necessary to build some packages
• include -- ditto

None of these strike me as needing to be enabled by default. My 2-cents...

[thomas_mueller_ffb]

patch with initial implementation

[osimons]

This patch was committed in [525] without closing the ticket. Closing now.