• Show log

    Commit

  • Hash : 5ddf1007
    Author : Stefano Lattarini
    Date : 2012-10-27T16:41:39

    tests: prefer including 'test-init.sh' rather than './defs'
    
    This is a follow-up to today's commit v1.12.4-22-g0610fc8,
    "tests: prepare to move ./defs to t/ax/test-init.sh"
    
    * All tests: To run the common setup, use the command:
    
        . test-init.sh
    
    instead of the older, "historical" one:
    
        . ./defs || exit 1
    
    Note that the "|| exit 1" wasn't really useful, since the 'errexit'
    shell flag is in effect in both './defs' and 'test-init.sh', and all
    the known shells that are good enough to run the automake testsuite
    do automatically exit with error when a sourced file cannot be found
    (at least, they do so in non-interactive mode, which is the only
    mode that concerns us in the testsuite).
    
    * t/ax/tap-summary-aux.sh, t/ax/testsuite-summary-checks.sh: Likewise.
    
    * gen-testsuite-part: Do the same in the generated tests.
    
    Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
    

  • README

  • This is the 'contrib' directory of the GNU Automake distribution.
    
    Here you'll find additions to the Automake base distribution, in form of
    makefile fragments, m4 macros, scripts, documentation, et cetera.  Such
    addition that might be useful for a significant percentage of its general
    audience, but (for one reason or another) are not deemed appropriate for
    inclusion into the Automake core.
    
    There are several reasons for which a feature can be kept in contrib:
    
      1. The long-term usefulness of the feature is debatable and uncertain;
         on-field and real-word testing are necessary to prove or disprove
         its usefulness, before the feature can be committed into the Automake
         core (as doing so too early would later force us to continue the
         support for backward-compatibility, even if the features proves
         flawed or fails to attract widespread use).
    
      2. The APIs or overall design of the feature are still unstable, and
         need on-field testing to iron warts and usability bugs, or uncover
         potential flaws.
    
      3. The feature was an historical one, mostly obsoleted but still used
         "here and there" in the wild; so we want to to deprecate it and
         remove it from the Automake core, but cannot remove it altogether,
         for the sake of those still-existing usage.  So it gets moved in
         contrib.