From: Alexandre Oliva Date: Thu, 29 Apr 1999 10:48:23 +0000 (+0000) Subject: removed automake-specific policies X-Git-Tag: release-1-3~7 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1993b5591ab069ab18f2660d42be20b945ad58e6;p=thirdparty%2Flibtool.git removed automake-specific policies --- diff --git a/README-alpha b/README-alpha index ea4e8b84e..7d024c5a9 100644 --- a/README-alpha +++ b/README-alpha @@ -21,31 +21,31 @@ using (by typing `ltconfig --version'). = 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 it is a large change, you must make sure they have signed the + appropriate paperwork, and 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. + and in the test case you write. * 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 libtool. These +* Some files in the libtool package are not owned by libtool. These files should never be edited here. These files are COPYING, INSTALL, - config.guess config.sub, install-sh, mdate-sh, mkinstalldirs, texinfo.tex + config.guess, config.sub, install-sh, mdate-sh, mkinstalldirs, + texinfo.tex. * Changes other than bug fixes must be mentioned in NEWS ================================================================ = Test suite -* Use "make check" and "make maintainer-check" liberally - -* Make sure each test file is executable +* Use "make check" liberally, on as many platforms as you can. Use as + many compilers and linkers you can. ================================================================ @@ -58,7 +58,7 @@ using (by typing `ltconfig --version'). * Update NEWS. -* Update the version number in configure.in and libtool.spec. +* 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.)