* NEWS: Likewise.
+2002-09-08 Alexandre Duret-Lutz <duret_g@epita.fr>
+
+ * automake.texi (Include): Fragments are always distributed.
+ * NEWS: Likewise.
+
2002-09-08 Andreas Buening <andreas.buening@nexgo.de>
Fix for automake/334:
a DESTDIR install.
* `+=' can be used in conditionals, even if the augmented variable
was defined for another condition.
+* Makefile fragments (inserted with `include') are always distributed.
* Use Autoconf's --trace interface to inspect configure.ac and get
a more accurate view of it.
* Add support for extending aclocal's default macro search path
compilation of the package. Since these variables are documented as
being for the package builder, that person rightfully expects to be able
to override any of these variables at build time.
-@c FIXME: maybe Automake could bark if a developer forces a user variable
-@c from Makefile.am.
To get around this problem, automake introduces an automake-specific
shadow variable for each user flag variable. (Shadow variables are not
Note that if a fragment is included inside a conditional, then the
condition applies to the entire contents of that fragment.
+Makefile fragments included this way are always distributed because
+there are needed to rebuild @file{Makefile.in}.
@node Conditionals, Gnits, Include, Top
@chapter Conditionals
-@set UPDATED 24 August 2002
-@set UPDATED-MONTH August 2002
+@set UPDATED 8 September 2002
+@set UPDATED-MONTH September 2002
@set EDITION 1.6c
@set VERSION 1.6c
-@set UPDATED 24 August 2002
-@set UPDATED-MONTH August 2002
+@set UPDATED 8 September 2002
+@set UPDATED-MONTH September 2002
@set EDITION 1.6c
@set VERSION 1.6c