--- loncom/build/Makefile	2007/03/20 01:51:39	1.182.4.6
+++ loncom/build/Makefile	2007/05/13 11:55:27	1.184
@@ -1,6 +1,6 @@
 # The LearningOnline Network with CAPA
 
-# $Id: Makefile,v 1.182.4.6 2007/03/20 01:51:39 albertel Exp $
+# $Id: Makefile,v 1.184 2007/05/13 11:55:27 albertel Exp $
 
 # TYPICAL USAGE of this Makefile is primarily for two targets:
 # "make build" and "make install".
@@ -22,7 +22,7 @@ SAVE=program.pl.$(TIMESTAMP)
 LAUNCHSAVE=$(OUTSTREAM) $(SAVE)
 METAMTARGET=""
 MTARGET=""
-VERSION=2.3.3
+VERSION=CVS_HEAD
 # The current working definition for "RELEASE" is: changes not in the software,
 # but in the operating system dependent packaging of the software.  Thus, the
 # generic tarball releases do not need to have a release number specified.
@@ -495,10 +495,10 @@ postinstall:
 VERSION:
 	install -d $(TARGET)/etc
 	echo -n "LON-CAPA release $(VERSION)-" > $(TARGET)/etc/loncapa-release
-	date +"%Y%m%d%H" >> $(TARGET)/etc/loncapa-release
+	date +"%Y%m%d" >> $(TARGET)/etc/loncapa-release
 	install -d $(TARGET)/home/httpd/html/lon-status
 	echo -n "$(VERSION)-" > $(TARGET)/home/httpd/html/lon-status/version.txt
-	date +"%Y%m%d%H" >> $(TARGET)/home/httpd/html/lon-status/version.txt
+	date +"%Y%m%d" >> $(TARGET)/home/httpd/html/lon-status/version.txt
 
 aboutVERSION:
 	cat $(SOURCE)/loncom/license/about.html | \
@@ -590,6 +590,10 @@ MANIFEST_all:
 	echo 'loncom/development_hosts.tab' >> $(SOURCE)/MANIFEST
 	echo 'loncom/production_domain.tab' >> $(SOURCE)/MANIFEST
 	echo 'loncom/development_domain.tab' >> $(SOURCE)/MANIFEST
+	echo 'loncom/production_dns_hosts.tab' >> $(SOURCE)/MANIFEST
+	echo 'loncom/development_dns_hosts.tab' >> $(SOURCE)/MANIFEST
+	echo 'loncom/production_dns_domain.tab' >> $(SOURCE)/MANIFEST
+	echo 'loncom/development_dns_domain.tab' >> $(SOURCE)/MANIFEST
 	# ------------------ Files needed for dynamically generated directories
 	echo 'doc/man' >> $(SOURCE)/MANIFEST
 	echo 'doc/lib' >> $(SOURCE)/MANIFEST