diff options
| author | rmanfredi <rmanfredi@190e5f8e-a817-0410-acf6-e9863daed9af> | 2006-08-25 21:54:31 +0000 |
|---|---|---|
| committer | rmanfredi <rmanfredi@190e5f8e-a817-0410-acf6-e9863daed9af> | 2006-08-25 21:54:31 +0000 |
| commit | 8e0de883d7513feefa92175f24b73d496ea0e93b (patch) | |
| tree | 31f7ac5c912985ea54c4831b91298a0086f4e062 /mcon/mconfig.SH | |
| parent | 65d0d69d2eaf1288f980ab404077792db6c5cdb8 (diff) | |
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: https://dist.svn.sourceforge.net/svnroot/dist/trunk/dist@4 190e5f8e-a817-0410-acf6-e9863daed9af
Diffstat (limited to 'mcon/mconfig.SH')
| -rwxr-xr-x | mcon/mconfig.SH | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/mcon/mconfig.SH b/mcon/mconfig.SH index 8fb6095..140fb6e 100755 --- a/mcon/mconfig.SH +++ b/mcon/mconfig.SH @@ -119,6 +119,11 @@ sub init { sub init_constants { $NEWMANI = 'MANIFEST.new'; # List of files to be scanned $MANI = 'MANIFEST'; # For manifake + + # The distinction between MANIFEST.new and MANIFEST can make sense + # when the "pat" tools are used, but if only metaconfig is used, then + # we can very well leave without a MANIFEST.new. --RAM, 2006-08-25 + $NEWMANI = $MANI if -f $MANI && ! -f $NEWMANI; } # Record the exceptions -- almost all symbols but these are lower case |