Edit

kc3-lang/automake/HACKING

Branch :

  • Show log

    Commit

  • Author : Tom Tromey
    Date : 1999-03-26 21:57:32
    Hash : a85ba428
    Message : * automake.in (am_install_var): Removed obsolete comment. * texinfos.am (uninstall-info): Don't print loop but instead print commands. Simplified pre-uninstall loop. * scripts.am (uninstall-@DIR@SCRIPTS): Don't print loop but instead print commands. * progs.am (uninstall-@DIR@PROGRAMS): Don't print loop but instead print commands. * ltlib.am (uninstall-@DIR@LTLIBRARIES): Don't print loop but instead print commands. * lisp.am (install-@DIR@LISP): Strip subdir from file name. (uninstall-@DIR@LISP): Likewise. Also, don't print loop but instead print commands. * libs.am (uninstall-@DIR@LIBRARIES): Don't print loop but instead print commands. * java.am (uninstall-@DIR@JAVA): Don't print loop but instead print commands. * header.am (install-@DIR@HEADERS): Strip subdir from file name. (uninstall-@DIR@HEADERS): Likewise. Also, don't print loop but instead print commands. * data.am (install-@DIR@DATA): Strip subdir from file name. (uninstall-@DIR@DATA): Likewise. Also, don't print loop but instead print commands.

  • HACKING
  • ================================================================
    = This file
    
    * This file attempts to describe the rules to use when hacking
      automake.
    
    * Don't put this file into the distribution.  Don't mention it in the
      ChangeLog.
    
    
    ================================================================
    = Administrivia
    
    * If you incorporate a change from somebody on the net:
      First, if it is a large change, you must make sure they have signed the
      appropriate paperwork.
      Second, be sure to add their name and email address to THANKS
    
    * If a change fixes a test, mention the test in the ChangeLog entry.
    
    * If somebody reports a new bug, mention his name in the ChangeLog entry
      and in the test case you write.  Put him into THANKS.
    
    * The correct response to most actual bugs is to write a new test case
      which demonstrates the bug.  Then fix the bug, re-run the test suite,
      and check everything in.
    
    * Some files in the automake package are not owned by automake.  These
      files should never be edited here.  These files are COPYING, INSTALL,
      ansi2knr.1, ansi2knr.c, config.guess config.sub, install-sh, mdate-sh,
      missing, mkinstalldirs, texinfo.tex
    
    * Changes other than bug fixes must be mentioned in NEWS
    
    
    ================================================================
    = Editing `.am' files
    
    * Always use $(...) and not ${...}
    
    * Use `:', not `true'.  Use `exit 1', not `false'.
    
    * Use `##' comments liberally.  Comment anything even remotely
      unusual.
    
    * Never use basename or dirname.  Instead use sed
    
    * For install and uninstall rules, if a loop is required, it should be
      silent.  Then the body of the loop itself should print each
      "important" comman it runs.  The printed commands should be preceded
      by a single space.
    
    
    ================================================================
    = Editing automake.in and aclocal.in
    
    * Follow existing indentation style.
    
    * Use only Perl 4 constructs
    
    
    ================================================================
    = Test suite
    
    * Use "make check" and "make maintainer-check" liberally
    
    * Make sure each test file is executable
    
    
    ================================================================
    = Release procedure
    
    * Fetch new versions of the files that are maintained by the FSF.
      Commit.  Unfortunately you need an FSF account to do this.
    
    * Update NEWS.  For an alpha release, update README-alpha.
    
    * Update the version number in configure.in.
      (The idea is that every other alpha number will be a net release.
      The repository will always have its own "odd" number so we can easily
      distinguish net and repo versions.)
    
    * Configure, build, and install.
    
    * Run aclocal, automake, and autoconf.
    
    * Commit
    
    * Run `make cvs-dist'
    
    * Put new release on ftp site and send announcement.
      (If not an alpha, announcement must also go to FSF.)
    
    * Update version number in configure.in to next alpha number.
      Re-run autoconf and commit.