summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--gettext-tools/doc/ChangeLog5
-rw-r--r--gettext-tools/doc/gettext.texi22
2 files changed, 26 insertions, 1 deletions
diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog
index aef03ce..278da89 100644
--- a/gettext-tools/doc/ChangeLog
+++ b/gettext-tools/doc/ChangeLog
@@ -1,3 +1,8 @@
+2005-02-05 Bruno Haible <bruno@clisp.org>
+
+ * gettext.texi (Release Management): New section.
+ Suggested by Karl Berry.
+
2005-02-04 Bruno Haible <bruno@clisp.org>
* gettext.texi (Plural forms): Add info about Vietnamese.
diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index 00e1aa6..294323b 100644
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -292,6 +292,7 @@ The Maintainer's View
* Adjusting Files:: Files You Must Create or Alter
* autoconf macros:: Autoconf macros for use in @file{configure.in}
* CVS Issues:: Integrating with CVS
+* Release Management:: Creating a Distribution Tarball
Files You Must Create or Alter
@@ -6252,6 +6253,7 @@ for changes.
* Adjusting Files:: Files You Must Create or Alter
* autoconf macros:: Autoconf macros for use in @file{configure.in}
* CVS Issues:: Integrating with CVS
+* Release Management:: Creating a Distribution Tarball
@end menu
@node Flat and Non-Flat, Prerequisites, Maintainers, Maintainers
@@ -7138,7 +7140,7 @@ library support, like SCO.
@file{iconv.m4} is distributed with the GNU gettext package because
@file{gettext.m4} relies on it.
-@node CVS Issues, , autoconf macros, Maintainers
+@node CVS Issues, Release Management, autoconf macros, Maintainers
@section Integrating with CVS
Many projects use CVS for distributed development, version control and
@@ -7262,6 +7264,24 @@ and adds to the package's pre-build script an invocation of
@include autopoint.texi
+@node Release Management, , CVS Issues, Maintainers
+@section Creating a Distribution Tarball
+
+@cindex release
+@cindex distribution tarball
+In projects that use GNU @code{automake}, the usual commands for creating
+a distribution tarball, @samp{make dist} or @samp{make distcheck},
+automatically update the PO files as needed.
+
+If GNU @code{automake} is not used, the maintainer needs to perform this
+update before making a release:
+
+@example
+$ ./configure
+$ (cd po; make update-po)
+$ make distclean
+@end example
+
@node Programming Languages, Conclusion, Maintainers, Top
@chapter Other Programming Languages