maint: improve README instructions for fetching latest version.

* README, README-alpha (Obtaining the Latest Sources): New
section, describing use of savannah repositories and bootstrap.
* README.alpha (Reporting Bugs): Remove git instructions in
favour of a reference to the new `Obtaining the Latest Sources'
section.
This commit is contained in:
Gary V. Vaughan 2010-09-16 09:47:45 +07:00
parent 92d9818d7e
commit bb8ae2a29a
3 changed files with 104 additions and 13 deletions

View File

@ -58,6 +58,15 @@
cross), and for the specific case of MSVC on Cygwin it makes the
test pass.
2010-09-15 Gary V. Vaughan <gary@gnu.org>
maint: improve README instructions for fetching latest version.
* README, README-alpha (Obtaining the Latest Sources): New
section, describing use of savannah repositories and bootstrap.
* README.alpha (Reporting Bugs): Remove git instructions in
favour of a reference to the new `Obtaining the Latest Sources'
section.
2010-09-14 Eric Blake <eblake@redhat.com>
maint: ship .xz, not .lzma

47
README
View File

@ -113,7 +113,51 @@ 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,
<bug-libtool@gnu.org>.
4. Version Numbering
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:anonymous@pserver.git.sv.gnu.org:/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
5. Version Numbering
====================
People have complained that they find the version numbering scheme under
@ -168,7 +212,6 @@ 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.

View File

@ -21,21 +21,17 @@ subject line including the string `[PLATFORM]'.
=================
If this distribution doesn't work for you, before you report the
problem, please try upgrading to the latest version from git first:
git clone git://git.savannah.gnu.org/libtool.git
cd libtool
./bootstrap
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. To use it, you need a recent
(maybe yet to be released) version of both Autoconf and Automake. If
you don't intend to run the test suite, you can speed up the `bootstrap'
step by an order of magnitude if you call it like this instead:
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 not fixed in the latest version, please send a full
If your bug is still not fixed in the latest version, please send a full
report to <bug-libtool@gnu.org>, 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).
@ -71,7 +67,7 @@ do it like this:
gmake check TESTS="tests/cdemo-static.test tests/cdemo-static-make.test \
tests/cdemo-static-exec.test" \
TESTSUITEFLAGS=-V
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
@ -109,6 +105,49 @@ 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,
<bug-libtool@gnu.org>.
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:anonymous@pserver.git.sv.gnu.org:/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.