Let metaconfig use the MANIFEST file if there is no MANIFEST.new.

The MANIFEST.new file is necessary when using the "pat" tools, but not
when running metaconfig by itself.


git-svn-id: svn://svn.code.sf.net/p/dist/code/trunk/dist@4 2592e710-e01b-42a5-8df0-11608a6cc53d

1 files changed, 7 insertions, 1 deletions

diff --git a/mcon/man/mconfig.SH b/mcon/man/mconfig.SH
index 059091b..44a6ae5 100755
--- a/mcon/man/mconfig.SH
+++ b/mcon/man/mconfig.SH
@@ -159,7 +159,8 @@ your .SH file).
 .IP \(bu
 Create a MANIFEST.new file in your top level directory that lists all the
 files in your package. This file will remain private and will not be
-part of the final distribution.
+part of the final distribution. (As a convenience, the MANIFEST file will
+be used by \fImetaconfig\fR if there is no MANIFEST.new file yet.)
 The filename should be the first field on each line.
 After some whitespace you can add a short comment describing your file.
 Only source files should be listed in there. The special file
@@ -972,6 +973,11 @@ it uses its units and your source code to produce all the needed configuration
 files. If you intend to write new units, you should have a good understanding
 of the whole scheme.
 .PP
+If there is no MANIFEST.new file, \fImetaconfig\fR will try to use the
+MANIFEST file instead, for convenience.  Everywhere we mention MANIFEST.new,
+it can be understood as MANIFEST provided there is no MANIFEST.new file
+found at the root of your package.
+.PP
 Assuming your MANIFEST.new file is properly set and lists all the source
 files you wish to configure, and that you have run \fIpackint\fR in your
 root source directory to create a \fI.package\fR file, you may run