[SCM] GNU Libtool branch, master, updated. v2.2.10-199-g3ce5708

[Gary V. Vaughan]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Libtool".

The branch, master has been updated
       via  3ce570843e0f83e0c7d4b331945e7aff98ad6878 (commit)
       via  28956db0f0b80c3dd88307e29ce13ef9a68ecc47 (commit)
       via  14df28e4f478ce58cd0472f31aaf1f4c91ef9c6b (commit)
       via  aded917934bd13a2a5a390e2c6bc22d913da0f37 (commit)
       via  a42ab2b857499d6a5b004849cefe813938f4a2ba (commit)
       via  9837f9a545d494890b5b7c4ba7030bda1c49935e (commit)
      from  8e7350625f1236f6f0c31ba5a8f518671731b032 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3ce570843e0f83e0c7d4b331945e7aff98ad6878
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 12:08:13 2010 +0700

    maint: use sed instead of maintaining 2 README files.
    
    * README.alpha: Deleted.  It was mostly identical to README.
    * libltdl/config/edit-readme-alpha: New script to edit the
    contents of README in the dist tree prior to tarring up.
    * Makefile.am (dist-hook): Run it before rolling alpha release
    tarball.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

commit 28956db0f0b80c3dd88307e29ce13ef9a68ecc47
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 11:13:50 2010 +0700

    maint: improve README's `Obtaining the Latest Sources'.
    
    * README (Obtaining the Latest Sources): Add instructions for
    obtaining stable, alpha and nightly snapshot tarballs.
    * README.alpha (Obtaining the Latest Sources): Adjust to match.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

commit 14df28e4f478ce58cd0472f31aaf1f4c91ef9c6b
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 10:46:09 2010 +0700

    maint: reformat README `The Test Suites' for consistency.
    
    * README (The Test Suites): Reformatted for consistency.
    * README.alpha (The Test Suites): Adjust to match.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

commit aded917934bd13a2a5a390e2c6bc22d913da0f37
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 10:38:10 2010 +0700

    maint: improve `Reporting Bugs' in README and README.alpha.
    
    * README (Reporting Bugs): Rewritten to a more complete and
    concise guide to providing a good bug report.
    * README.alpha (Reporting Bugs): Adjust to match.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

commit a42ab2b857499d6a5b004849cefe813938f4a2ba
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 10:08:25 2010 +0700

    maint: consolidate Introductions of README and README.alpha.
    
    * README (Introduction): Rewritten to a more logical order for
    first time users, incorporating some additional text that was
    previously only in README.alpha.
    * README.alpha (Introduction): Adjust to match.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

commit 9837f9a545d494890b5b7c4ba7030bda1c49935e
Author: Gary V. Vaughan <address@hidden>
Date:   Sat Sep 18 09:48:31 2010 +0700

    maint: copy the Version Numbering section into README.alpha.
    
    * README.alpha (Version Numbering): No less useful for users
    of alpha releases.  Copied from README.
    
    Signed-off-by: Gary V. Vaughan <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                        |   33 ++++++++
 Makefile.am                      |   11 ++-
 README                           |  162 +++++++++++++++++++++++++++++--------
 README.alpha                     |  168 --------------------------------------
 libltdl/config/edit-readme-alpha |   81 ++++++++++++++++++
 5 files changed, 249 insertions(+), 206 deletions(-)
 delete mode 100644 README.alpha
 create mode 100755 libltdl/config/edit-readme-alpha

diff --git a/ChangeLog b/ChangeLog
index fd8bb49..946f8d7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -4,6 +4,39 @@
        * tests/ltdl-libdir.at (libdir of installed modules): Skip if
        $LIBLTDL does not exist.
 
+2010-09-18  Gary V. Vaughan  <address@hidden>
+
+       maint: use sed instead of maintaining 2 README files.
+       * README.alpha: Deleted.  It was mostly identical to README.
+       * libltdl/config/edit-readme-alpha: New script to edit the
+       contents of README in the dist tree prior to tarring up.
+       * Makefile.am (dist-hook): Run it before rolling alpha release
+       tarball.
+
+       maint: improve README's `Obtaining the Latest Sources'.
+       * README (Obtaining the Latest Sources): Add instructions for
+       obtaining stable, alpha and nightly snapshot tarballs.
+       * README.alpha (Obtaining the Latest Sources): Adjust to match.
+
+       maint: reformat README `The Test Suites' for consistency.
+       * README (The Test Suites): Reformatted for consistency.
+       * README.alpha (The Test Suites): Adjust to match.
+
+       maint: improve `Reporting Bugs' in README and README.alpha.
+       * README (Reporting Bugs): Rewritten to a more complete and
+       concise guide to providing a good bug report.
+       * README.alpha (Reporting Bugs): Adjust to match.
+
+       maint: consolidate Introductions of README and README.alpha.
+       * README (Introduction): Rewritten to a more logical order for
+       first time users, incorporating some additional text that was
+       previously only in README.alpha.
+       * README.alpha (Introduction): Adjust to match.
+
+       maint: copy the Version Numbering section into README.alpha.
+       * README.alpha (Version Numbering): No less useful for users
+       of alpha releases.  Copied from README.
+
 2010-09-17  Peter Rosin  <address@hidden>
 
        tests: actually detect missing 'test' in 'if "$foo" = ...'.
diff --git a/Makefile.am b/Makefile.am
index dcd0876..6e29a29 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -406,6 +406,10 @@ install-data-local: libltdl/Makefile.in
 ## Distribution. ##
 ## ------------- ##
 
+edit_readme_alpha = $(auxdir)/edit-readme-alpha
+
+EXTRA_DIST += $(edit_readme_alpha)
+
 uninstall-hook:
        @$(NORMAL_UNINSTALL)
        @list='$(ltdldatafiles) $(auxfiles)'; for f in $$list; do \
@@ -419,11 +423,10 @@ uninstall-hook:
        done
 
 dist-hook:
-## Ship README.alpha only in alpha release, but renamed to README
-       @if test -f $(srcdir)/README.alpha; then \
+## Edit the README file for alpha releases.
        case $(VERSION) in \
-         *[a-z]) cp -p $(srcdir)/README.alpha $(distdir)/README ;; \
-       esac; else :; fi
+         *[a-z]) $(SHELL) $(srcdir)/$(edit_readme_alpha) $(distdir)/README ;; \
+       esac
 ## Ensure aclocal has not wrongly picked up old macro definitions.
        for macro in LT_INIT AC_PROG_LIBTOOL AM_PROG_LIBTOOL; do \
          if grep $$macro $(srcdir)/aclocal.m4 $(srcdir)/libltdl/aclocal.m4; 
then \
diff --git a/README b/README
index 16328bb..f88901c 100644
--- a/README
+++ b/README
@@ -8,32 +8,70 @@ This is GNU Libtool, a generic library support script.  
Libtool hides
 the complexity of using shared libraries behind a consistent, portable
 interface.
 
-To use Libtool, add the new generic library building commands to your
-Makefile, Makefile.in, or Makefile.am.  See the documentation for
-details.
-
 Libtool's home page is:
 
-  http://www.gnu.org/software/libtool/libtool.html
+    http://www.gnu.org/software/libtool/libtool.html
 
 See the file NEWS for a description of recent changes to Libtool.
 
-See the file INSTALL for generic instructions on how to build and install
-Libtool.  Please see the file doc/notes.txt for some platform-specific
-information.  Please note that you need GNU make to build Libtool.
+Please note that you can build GNU Libtool from this directory using a
+vendor Make program as long as this is an official release tarball;
+otherwise you will need GNU Make for sane VPATH support.  See the file
+INSTALL for complete generic instructions on how to build and install
+Libtool.  Also, see the file doc/notes.txt for some platform- specific
+information.
+
+See the info node (libtool)Tested Platforms. (or the file doc/PLATFORMS)
+for a list of platforms that Libtool already supports.
 
-See the info node (libtool)Tested Platforms. (or the file
-doc/PLATFORMS) for a list of platforms that Libtool supports.
+Please try it on all the platforms you have access to:
+
+ * If it builds and passes the test suite (`gmake check'), please send
+   a short note to the libtool mailing list <address@hidden> with a
+   subject line including the string `[PLATFORM]', and containing the
+   details from the end of `./libtool --help' in the body.
+ * Otherwise, see `Reporting Bugs' below for how to help us fix any
+   problems you discover.
+
+To use Libtool, add the new generic library building commands to your
+Makefile, Makefile.in, or Makefile.am.  See the documentation for
+details.
 
 
 2. Reporting Bugs
 =================
 
-If you have any suggestions or bug reports, or you wish to port Libtool
-to a new platform, please send electronic mail to the libtool mailing
-list <address@hidden> or bug reports to <address@hidden>.  Be sure
-to send us your information from the end of the help message given by
-`./libtool --help'.
+If this distribution doesn't work for you, before you report the
+problem, at least try upgrading to the latest released version first,
+and see whether the issue persists.  If you feel able, you can also
+check whether the issue has been fixed in the development sources for
+the next release (see `Obtaining the Latest Sources' below).
+
+Once you've determined that your bug is still not fixed in the latest
+version, please send a full report to <address@hidden>, including:
+
+  1. the information from the end of the help message given by
+     `./libtool --help', and the verbose output of any failed tests
+     (see `The Test Suites' immediately below);
+  2. complete instructions for how to reproduce your bug, along with
+     the results you were expecting, and how they differ from what you
+     actually see;
+  3. a workaround or full fix for the bug, if you have it;
+  4. a copy of `tests/testsuite.log' if you are experiencing failures
+     in the Autotest testsuite.
+  5. new test cases for the testsuite that demonstrate the bug are
+     especially welcome, and will help to ensure that future releases
+     don't reintroduce the problem - if you're not able to write a
+     complete testsuite case, a simple standalone shell script is
+     usually good enough to help us write a test for you.
+
+If you have any other suggestions, or if you wish to port Libtool to a
+new platform, please send email to the mailing list <address@hidden>.
+
+Please note that if you send us an non-trivial code for inclusion in a
+future release, we may ask you for a copyright assignment (for brief
+details see the `Copyright Assignment' section on our `Contributing'
+webpage <http://www.gnu.org/software/libtool/contribute.html>).
 
 
 3. The Test Suites
@@ -43,15 +81,15 @@ Libtool comes with two integrated sets of tests to check 
that your build
 is sane.  You can run both test suites like this, assuming that `gmake'
 refers to GNU make:
 
-  gmake -k check
+    gmake -k check
 
 If you want to run the old testsuite only, do it like this:
 
-  gmake check TESTSUITEFLAGS=-V
+    gmake check TESTSUITEFLAGS=-V
 
 If you want to run the new testsuite only, do it like this:
 
-  gmake check-local
+    gmake check-local
 
 The tests of the old test suite run in groups in the various demo
 subdirectories, so if one of the tests early in a group FAILs, the rest
@@ -64,9 +102,8 @@ To run a test group of the old test suite in isolation (say, 
you think
 you have fixed a bug, but don't want to rerun the entire suite), you can
 do it like this:
 
-  gmake check TESTS="tests/cdemo-static.test tests/cdemo-static-make.test \
-                     tests/cdemo-static-exec.test" \
-              TESTSUITEFLAGS=-V
+    gmake check TESTSUITEFLAGS=-V TESTS="tests/cdemo-static.test \
+        tests/cdemo-static-make.test tests/cdemo-static-exec.test"
 
 Providing that you have a FAIL from the most recent group from a
 particular demo directory (like the cdemo-static.test group above), you
@@ -82,40 +119,89 @@ the verbose output from all failed tests.
 In order to enable debug shell tracing, you can set VERBOSE=debug when
 running the old test suite.
 
+In the long run, Libtool will move to using only the new, Autotest-
+driven testsuite.  Its usage is documented in:
 
-In the long run, Libtool will move to using only the new,
-Autotest-driven testsuite.  Its usage is documented in
-
-  info Autoconf 'testsuite Invocation'
+    info Autoconf 'testsuite Invocation'
 
-but simple help may also be obtained through
+but simple help may also be obtained through:
 
-  gmake check-local TESTSUITEFLAGS='--help'
+    gmake check-local TESTSUITEFLAGS='--help'
 
 For verbose output, add the flag `-v', for running only a subset of the
 independent tests, merely specify them by number or by keyword, both of
 which are displayed with the `--list' flag.  For example, the `libtool'
 keyword is used for the tests that exercise only this script.  So it is
 possible to test an installed script, possibly from a different Libtool
-release, with
-  gmake check-local TESTSUITEFLAGS="-k libtool LIBTOOL=/path/to/libtool"
+release, with:
+
+    gmake check-local \
+        TESTSUITEFLAGS="-k libtool LIBTOOL=/path/to/libtool"
 
 Some tests, like the one exercising max_cmd_len limits, make use of this
 to invoke the testsuite recursively on a subset of tests.  For these
 tests, the variable INNER_TESTSUITEFLAGS may be used.  It will be
-expanded right after the `-k libtool', without separating whitespace,
-so that further limiting of the recursive set of tests is possible.
-For example, to run only the template tests within the max_cmd_len, use
-  gmake check-local TESTSUITEFLAGS="-v -x -k max_cmd_len \
+expanded right after the `-k libtool', without separating whitespace, so
+that further limiting of the recursive set of tests is possible.  For
+example, to run only the template tests within the max_cmd_len, use:
+
+    gmake check-local TESTSUITEFLAGS="-v -x -k max_cmd_len \
                      INNER_TESTSUITEFLAGS=',template -v -x'"
 
 If you wish to report test failures to the libtool list, you need to
 send the file `tests/testsuite.log' to the bug report mailing list,
 <address@hidden>.
 
+
 4. Obtaining the Latest Sources
 ===============================
 
+* With the exception of ancient releases, all official GNU Libtool
+  releases have a detached GPG signature file.  With this you can verify
+  that the corresponding file (i.e. without the `.sig' suffix) is the
+  same file that was released by the owner of it's GPG key ID.  First,
+  be sure to download both the .sig file and the corresponding release,
+  then run a command like this:
+
+    gpg --verify libtool-x.y.z.tar.gz.sig
+
+  If that command fails because you don't have the required public key,
+  then run this command to import it:
+
+    gpg --keyserver keys.gnupg.net --recv-keys 2983D606
+
+  and then rerun the `gpg --verify' command.
+
+* Official stable releases of GNU Libtool, along with these detached
+  signature files are available from:
+
+    ftp://ftp.gnu.org/gnu/libtool
+
+  To reduce load on the main server, please use one of the mirrors
+  listed at:
+
+    http://www.gnu.org/order/ftp.html
+
+* Alpha quality pre-releases of GNU Libtool, also with detached
+  signature files are available from:
+
+    ftp://alpha.gnu.org/gnu/libtool
+
+  and some of the mirrors listed at:
+
+    http://www.gnu.org/order/ftp.html
+
+* Nightly snapshots of the unreleased development trunk of GNU Libtool
+  are available from:
+
+    http://pogma.com/libtool
+
+  These files do not have signatures, but will allow you to easily
+  determine whether the most recent development code still exhibits any
+  bugs you have discovered, without requiring you to install a complete
+  build environment and the extra tools needed to bootstrap a version
+  control checkout.
+
 * The master libtool repository is stored in git.
 
   If you are a member of the savannah group for GNU Libtool, a writable
@@ -157,6 +243,14 @@ send the file `tests/testsuite.log' to the bug report 
mailing list,
   - Autoconf 2.59 or later
   - Automake 1.9.6 or later
 
+* The `bootstrap' script sets up the source directory for you to hack,
+  though it may take quite some time to run.  If you don't intend to
+  re-run the test suite, you can speed up the `bootstrap' step by an
+  order of magnitude if you call it like this instead:
+
+    reconfdirs='. libltdl' ./bootstrap
+
+
 5. Version Numbering
 ====================
 
@@ -212,7 +306,7 @@ things:
 For more details about version numbers, see:
 
     http://www.gnu.org/software/libtool/contribute.html
--- 
+--
   Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
   Foundation, Inc.
   Written by Gary V. Vaughan, 2004
diff --git a/README.alpha b/README.alpha
deleted file mode 100644
index a58167e..0000000
--- a/README.alpha
+++ /dev/null
@@ -1,168 +0,0 @@
-GNU Libtool
-***********
-
-1. Introduction
-===============
-
-This is an alpha testing release of GNU Libtool, please try it on all
-the platforms you have access to.  Using it more or less implicitly
-signs you up to help us find whatever problems you report.
-
-See the file INSTALL for generic instructions on how to build and install
-Libtool.  Please see the file doc/notes.txt for some platform-specific
-information.  Please note that you need GNU make to build Libtool.
-
-If it builds and passes the test suite (`gmake check'), please send
-notification to the libtool mailing list <address@hidden> with a
-subject line including the string `[PLATFORM]'.
-
-
-2. Reporting Bugs
-=================
-
-If this distribution doesn't work for you, before you report the
-problem, please try upgrading to the latest version first (see
-`Obtaining the latest sources' below).
-
-The `bootstrap' script sets up the source directory for you to hack,
-though it may take quite some time to run.  If you don't intend to
-re-run the test suite, you can speed up the `bootstrap' step by an
-order of magnitude if you call it like this instead:
-
-  reconfdirs='. libltdl' ./bootstrap
-
-If your bug is still not fixed in the latest version, please send a full
-report to <address@hidden>, including the information from the end
-of the help message given by `./libtool --help', and the verbose output
-of any failed test groups (as described below).
-
-
-3. The Test Suites
-==================
-
-Libtool comes with two integrated sets of tests to check that your build
-is sane.  You can run both test suites like this, assuming that `gmake'
-refers to GNU make:
-
-  gmake -k check
-
-If you want to run the old testsuite only, do it like this:
-
-  gmake check TESTSUITEFLAGS=-V
-
-If you want to run the new testsuite only, do it like this:
-
-  gmake check-local
-
-The tests of the old test suite run in groups in the various demo
-subdirectories, so if one of the tests early in a group FAILs, the rest
-of the tests in that group will be SKIPped.  If you see a FAIL further
-into a group, even if a test with the same name PASSes in another test
-group, you need to take note of the name of the first test in the group
-if you want to rerun the group with FAILures to get verbose output.
-
-To run a test group of the old test suite in isolation (say, you think
-you have fixed a bug, but don't want to rerun the entire suite), you can
-do it like this:
-
-  gmake check TESTS="tests/cdemo-static.test tests/cdemo-static-make.test \
-                     tests/cdemo-static-exec.test" \
-              TESTSUITEFLAGS=-V
-
-Providing that you have a FAIL from the most recent group from a
-particular demo directory (like the cdemo-static.test group above), you
-can explore the state of the directory to help with debugging.
-
-If you wish to report a test group failure to the libtool list, you need
-to send the verbose output of the FAILing group, along with the
-information from the end of `$(top_builddir)/libtool --help' to the bug
-report mailing list, <address@hidden> with a subject line that
-includes the string `[TEST FAILURE]'.  The file test-suite.log contains
-the verbose output from all failed tests.
-
-In order to enable debug shell tracing, you can set VERBOSE=debug when
-running the old test suite.
-
-
-In the long run, Libtool will move to using only the new,
-Autotest-driven testsuite.  Its usage is documented in
-
-  info Autoconf 'testsuite Invocation'
-
-but simple help may also be obtained through
-
-  gmake check-local TESTSUITEFLAGS='--help'
-
-For verbose output, add the flag `-v', for running only a subset of the
-independent tests, merely specify them by number or by keyword, both of
-which are displayed with the `--list' flag.  For example, the `libtool'
-keyword is used for the tests that exercise only this script.  So it is
-possible to test an installed script, possibly from a different Libtool
-release, with
-  gmake check-local TESTSUITEFLAGS="-k libtool LIBTOOL=/path/to/libtool"
-
-If you wish to report test failures to the libtool list, you need to
-send the file `tests/testsuite.log' to the bug report mailing list,
-<address@hidden>.
-
-4. Obtaining the Latest Sources
-===============================
-
-* The master libtool repository is stored in git.
-
-  If you are a member of the savannah group for GNU Libtool, a writable
-  copy of the libtool repository can be obtained by:
-
-    git clone <savannah-user>@git.sv.gnu.org:/srv/git/libtool.git
-
-  If you are behind a firewall that blocks the git protocol, you may
-  find it useful to use
-
-    git config --global url.http://git.sv.gnu.org/r/.insteadof \
-      git://git.sv.gnu.org/
-
-  to force git to transparently rewrite all savannah git references to
-  use http.
-
-  If you are not a member of the savannah group for GNU Libtool, you can
-  still fetch a read-only copy with either:
-
-    git clone git://git.sv.gnu.org/libtool.git
-
-  or using the CVS pserver protocol:
-
-    cvs -d:pserver:address@hidden:/srv/git/libtool.git \
-        co -d libtool HEAD
-
-* Before you can build from git, you need to bootstrap.  This requires:
-  - Autoconf 2.62 or later
-  - Automake 1.11.1 or later
-  - Help2man 1.29 or later
-  - Xz 4.999.8beta or later (from <http://tukaani.org/xz>)
-  - Texinfo 4.8 or later
-  - Any prerequisites of the above (such as m4, perl, tex)
-
-  Note that these bootstrapping dependencies are much stricter than
-  those required to use a destributed release for your own packages.
-  After installation, GNU Libtool is designed to work either standalone,
-  or optionally with:
-  - Autoconf 2.59 or later
-  - Automake 1.9.6 or later
--- 
-  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
-  Foundation, Inc.
-  Written by Gary V. Vaughan, 2004
-
-  This file is part of GNU Libtool.
-
-Copying and distribution of this file, with or without modification,
-are permitted in any medium without royalty provided the copyright
-notice and this notice are preserved.  This file is offered as-is,
-without warranty of any kind.
-
-
-Local Variables:
-mode: text
-fill-column: 72
-End:
-vim:tw=72
diff --git a/libltdl/config/edit-readme-alpha b/libltdl/config/edit-readme-alpha
new file mode 100755
index 0000000..6070a31
--- /dev/null
+++ b/libltdl/config/edit-readme-alpha
@@ -0,0 +1,81 @@
+#! /bin/sh
+
+#   edit-readme-alpha - edit README file for alpha releases
+#   Copyright (C) 2010 Free Software Foundation, Inc.
+#   Written by Gary V. Vaughan, 2010
+#
+#   This file is part of GNU Libtool.
+#
+# GNU Libtool is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License as
+# published by the Free Software Foundation; either version 2 of
+# the License, or (at your option) any later version.
+#
+# GNU Libtool is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with GNU Libtool; see the file COPYING.  If not, a copy
+# can be downloaded from  http://www.gnu.org/licenses/gpl.html,
+# or obtained by writing to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+####
+
+# We used to maintain separate (but extremely similiar!) README and
+# README.alpha files, and had `make dist' include the right one in a
+# distribution based on the contests of `$(VERSION)'.
+#
+# Now, we have `make dist' call this script to tweak the first paragraph
+# of README in situ, to be more suitable for an alpha quality release.
+
+EXIT_SUCCESS=0
+EXIT_FAILURE=1
+
+# Work around backward compatibility issue on IRIX 6.5. On IRIX 6.4+, sh
+# is ksh but when the shell is invoked as "sh" and the current value of
+# the _XPG environment variable is not equal to 1 (one), the special
+# positional parameter $0, within a function call, is the name of the
+# function.
+progpath="$0"
+
+# The name of this program:
+progname=`echo "$progpath" |sed 's|^.*/||'`
+
+
+# func_fatal_error ARG...
+# -----------------------
+# Echo program name prefixed message to standard error, and exit.
+func_fatal_error ()
+{
+    echo "$progname: $*" >&2
+    exit $EXIT_FAILURE
+}
+
+
+for file in "$@"; do
+  # Make sure the paragraph we are matching has not been edited since
+  # this script was written.
+  matched=`sed -n -e '/^This is GNU Libtool,/,/^interface.$/p' $file \
+      |wc -l |sed 's|^ *||'`
+  test 3 = "$matched" \
+      || func_fatal_error "$file format has changed, please fix \`$0'"
+
+  # Don't leave file droppings.
+  trap 'x=$?; rm $file.T; exit $x' 1 2 13 15
+
+  # Edit the first paragraph to be suitable for an alpha release.
+  sed -e '/^This is GNU Libtool,/,/^interface.$/c\
+This is an alpha testing release of GNU Libtool, a generic library\
+support script.  Libtool hides the complexity of using shared libraries\
+behind a consistent, portable interface.' $file > $file.T
+
+  # Diagnose redirection failure.
+  test -f $file.T || func_fatal_error "Unable to write $file.T"
+
+  # Overwrite the original file with our edited version.
+  mv $file.T $file || func_fatal_error "Unable to edit $file"
+done
+
+exit $EXIT_SUCCESS


hooks/post-receive
-- 
GNU Libtool