From e3761a57173285f23e041c47162dcc7016564128 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Wed, 3 Jan 1996 18:57:10 +0000 Subject: [PATCH] Doc update. Moved to 0.27 --- ChangeLog | 2 ++ automake.texi | 18 ++++++++++++++++-- configure.in | 2 +- version.texi | 2 +- 4 files changed, 20 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 6b12692..fdd4ce5 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ Wed Jan 3 00:05:40 1996 Tom Tromey + * configure.in (VERSION): Version 0.27. + * depend.am ($(srcdir)/.deps/%.P): Must regexp-quote srcdir in sed invocation. diff --git a/automake.texi b/automake.texi index 56d10ed..7f375cb 100644 --- a/automake.texi +++ b/automake.texi @@ -86,6 +86,7 @@ documents version @value{VERSION}. * Introduction:: Automake's purpose * Details:: Creating an Automake template file * Invoking automake:: Creating a Makefile.in +* Distributing:: Distributing generated Makefile.ins * Future:: Some ideas for the future. * Some index:: Index of variables @end menu @@ -329,8 +330,8 @@ Sometimes it is useful to determine the programs that are to be built at configure time. For instance, GNU @code{cpio} only builts @code{mt} and @code{rmt} under special circumstances. -In this case, you must notify Automake of all the programs that can -possibly be built, but at the same time cause the generated +In this case, you must notify @code{Automake} of all the programs that +can possibly be built, but at the same time cause the generated @file{Makefile.in} to use the programs specified by @code{configure}. This is done trivially by making the @code{PROGRAMS} variable determined at configure time, and letting @code{automake} look in the install @@ -765,6 +766,19 @@ This second mode is most often used by @code{make} itself, when it notices that a @code{Makefile.in} is out of date. +@node Distributing +@chapter Distributing @file{Makefile.in}s + +Automake places no restrictions on the distribution of the resulting +@file{Makefile.in}s. We still encourage software authors to distribute +their work under terms like those of the GPL, but doing so is not +required to use Automake. + +Some of the files that can be automatically installed via the +@samp{--install-missing} switch do fall under the GPL; examine each file +to see. + + @node Future @chapter Some ideas for the future diff --git a/configure.in b/configure.in index e9b8e52..bd93503 100644 --- a/configure.in +++ b/configure.in @@ -6,7 +6,7 @@ dnl AC_CONFIG_HEADER(config.h) PACKAGE=automake AC_SUBST(PACKAGE) AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE") -VERSION=0.26 +VERSION=0.27 AC_SUBST(VERSION) AC_DEFINE_UNQUOTED(VERSION, "$VERSION") ALL_LINGUAS= diff --git a/version.texi b/version.texi index 8ed3371..4ad65a8 100644 --- a/version.texi +++ b/version.texi @@ -1,3 +1,3 @@ -@set UPDATED 12 December +@set UPDATED 3 January @set EDITION 0.26 @set VERSION 0.26 -- 2.7.4