1 This is an alpha testing release of GNU Libtool. To get the latest
2 CVS version of this package, do:
5 cvs -z3 -d :ext:anoncvs@savannah.gnu.org:/cvsroot/libtool co libtool
9 The `bootstrap' script sets up the source directory for you to hack. To
10 use it, you need a recent (maybe yet to be released) version of both
11 Autoconf and Automake.
13 If you have any suggestions or bug reports, or you wish to port
14 libtool to a new platform, please send electronic mail to the libtool
15 mailing list <libtool@gnu.org> or bug reports to <bug-libtool@gnu.org>.
16 Don't forget to mention the version of libtool that you are currently
17 using (by typing `libtool --version').
19 ================================================================
22 * If you incorporate a change from somebody on the net:
23 If it is a large change, you must make sure they have signed the
24 appropriate paperwork, and be sure to add their name and email
27 * If a change fixes a test, mention the test in the ChangeLog entry.
29 * If somebody reports a new bug, mention his name in the ChangeLog entry
30 and in the test case you write.
32 * The correct response to most actual bugs is to write a new test case
33 which demonstrates the bug. Then fix the bug, re-run the test suite,
34 and check everything in.
36 * Some files in the libtool package are not owned by libtool. These
37 files should never be edited here. These files are:
57 * Changes other than bug fixes must be mentioned in NEWS
59 ================================================================
62 * Use "make check" liberally, on as many platforms as you can. Use as
63 many compilers and linkers you can.
66 ================================================================
69 * If you are a libtool maintainer, but have not yet registered your
70 gpg public key and (preferred) email address with the FSF, send an
71 email, preferably GPG-signed, to <ftp-upload@gnu.org> that includes
74 (a) name of package(s) that you are the maintainer for, and your
75 preferred email address.
77 (b) an ASCII armored copy of your GnuPG key, as an attachment.
78 ("gpg --export -a YOUR_KEY_ID > mykey.asc" should give you
81 When you have received acknowledgement of your message, the proper GPG
82 keys will be registered on ftp-upload.gnu.org and only then will you be
83 authorized to upload files to the FSF ftp machines.
85 * Update the version number in configure.ac.
86 See http://www.gnu.org/software/libtool/contribute.html for details of
89 * Update NEWS, ChangeLog.
93 * Run ./configure and then make.
95 * Run `make -fMakefile.maint fetch', which will fetch new versions of the
96 files that are maintained outside of libtool.
100 * Run `make -fMakefile.maint cvs-dist' which will build a release tarball
101 (with `make distcheck'), tag the tree with release-$(VERSION) and generate
102 the gpg signature files.
104 * Make sure you have a copy of xdelta installed, and a copy of the previous
105 release tarball in the build directory.
107 * Run 'make -fMakefile.maint deltas' (pass LASTRELEASE=min.maj[.mic[alpha]]
108 if needed) to create both diff and xdelta files between the previous
109 release tarball and the new with detached gpg signature files and clear
110 signed directive files.
112 * Upload release tarball, diff file and xdelta file, plus their associated
113 detached gpg signature files and clear signed directive files to
114 ftp-upload.gnu.org. If the upload is destined for ftp.gnu.org, then the
115 files should be placed in the /incoming/ftp directory. If the upload is
116 an alpha release destined for alpha.gnu.org, then the files should be
117 placed in the /incoming/alpha directory.
119 * Send announcement to libtool@gnu.org and autotools-announce@gnu.org,
120 if not an alpha send to info-gnu@gnu.org as well.
122 * Update version number in configure.ac to next alpha number.
123 See http://www.gnu.org/software/libtool/contribute.html for details of
124 the numbering scheme.
126 * Update NEWS, ChangeLog.
130 * Update the webpages, libtool.html will need to indicate the latest
131 release number and the news page should get a HTMLified copy of your
132 release announcement.
134 * If not an alpha, replace manual.html with the new one
135 (generate with `make -f Makefile.maint web-manual').
137 ================================================================
138 = Alpha release note template
140 To: libtool@gnu.org, autotools-announce@gnu.org
141 Subject: GNU Libtool @VERSION@ released (alpha release).
143 The Libtool Team is pleased to announce alpha release @VERSION@ of GNU
146 GNU Libtool hides the complexity of using shared libraries behind a
147 consistent, portable interface. GNU Libtool ships with GNU libltdl,
148 which hides the complexity of loading dynamic runtime libraries
149 (modules) behind a consistent, portable interface.
151 Here are the compressed sources:
153 ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz
154 ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2
156 Here are the xdeltas and diffs against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@:
158 ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
159 ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
161 Here are the gpg detached signatures:
163 ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz.sig
164 ftp://alpha.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2.sig
165 ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz.sig
166 ftp://alpha.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta.sig
168 Here are the MD5 and SHA1 checksums:
170 @MD5SUM@ libtool-@VERSION@.tar.gz
171 @MD5SUM@ libtool-@VERSION@.tar.bz2
172 @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
173 @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
174 @SHA1SUM@ libtool-@VERSION@.tar.gz
175 @SHA1SUM@ libtool-@VERSION@.tar.bz2
176 @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
177 @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
179 This release has @SUMMARY_OF_IMPROVEMENTS_SINCE_LAST_RELEASE_ON_THIS_BRANCH@.
181 This release was bootstrapped with @BOOTSTRAP_TOOLS_WITH_VERSIONS@,
182 but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
185 Alternatively, you can fetch the unbootstrapped sourcecode from
186 anonymous cvs by using the following commands:
189 $ cvs -z3 -d :ext:anoncvs@savannah.gnu.org:/cvsroot/libtool \
190 co -r @CVS_RELEASE_TAG@ libtool
192 You will then need to have recent (possibly as yet unreleased) versions
193 of Automake and Autoconf installed to bootstrap the checked out
196 New in @VERSION@: @RELEASE_DATE@
198 @EXCERPT_FROM_NEWS_FILE@
200 Please report bugs to <bug-libtool@gnu.org>.
202 ================================================================
203 = Full release note template
206 Cc: libtool@gnu.org, autotools-announce@gnu.org
207 Subject: GNU Libtool @VERSION@ released.
209 The Libtool Team is pleased to announce the release of GNU Libtool
212 GNU Libtool hides the complexity of using shared libraries behind a
213 consistent, portable interface. GNU Libtool ships with GNU libltdl,
214 which hides the comlexity of loading dynamic runtime libraries
215 (modules) behind a consistent, portable interface.
217 This release has @SUMMARY_OF_IMPROVEMENTS_SINCE_LAST_RELEASE_ON_THIS_BRANCH@.
219 New in @VERSION@: @RELEASE_DATE@
221 @EXCERPT_FROM_NEWS_FILE@
223 libtool-@VERSION@ is available now from ftp.gnu.org, along with
224 diffs and xdeltas against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@
225 that are also available from ftp.gnu.org. Please
226 use a mirror to reduce stress on the main gnu machine:
228 http://www.gnu.org/order/ftp.html
230 Here are the compressed sources:
232 ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz
233 ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2
235 Here are the xdeltas and diffs against libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@:
237 ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
238 ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
240 Here are the gpg detached signatures:
242 ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.gz.sig
243 ftp://ftp.gnu.org/gnu/libtool/libtool-@VERSION@.tar.bz2.sig
244 ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz.sig
245 ftp://ftp.gnu.org/gnu/libtool/libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta.sig
247 Here are the MD5 and SHA1 checksums:
249 @MD5SUM@ libtool-@VERSION@.tar.gz
250 @MD5SUM@ libtool-@VERSION@.tar.bz2
251 @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
252 @MD5SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
253 @SHA1SUM@ libtool-@VERSION@.tar.gz
254 @SHA1SUM@ libtool-@VERSION@.tar.bz2
255 @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.diff.gz
256 @SHA1SUM@ libtool-@PREV_RELEASE_VERSION_ON_THIS_BRANCH@-@VERSION@.xdelta
258 This release was bootstrapped with @BOOTSTRAP_TOOLS_WITH_VERSIONS@,
259 but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
262 Alternatively, you can fetch the unbootstrapped sourcecode from
263 anonymous cvs by using the following commands (just hit return when
264 you are prompted for the password):
267 $ cvs -z3 -d :ext:anoncvs@savannah.gnu.org:/cvsroot/libtool \
268 co -r @CVS_RELEASE_TAG@ libtool
270 You will then need to have the latest release versions of Automake
271 (@AUTOMAKE_VERSION@) and Autoconf (@AUTOCONF_VERSION@) installed to
272 bootstrap the checked out sources yourself.
274 Please report bugs to <bug-libtool@gnu.org>.