From: mh <mh>
Date: Sat, 22 Jun 2002 09:52:46 +0000 (+0000)
Subject: added UPGRADING tips
X-Git-Tag: MIR_1_0_0_RC1~75
X-Git-Url: http://erislabs.net/gitweb/?p=mir.git;a=commitdiff_plain;h=238254c1b04d15d5fb641311f80324433e9908c1

added UPGRADING tips
---

diff --git a/doc/INSTALL.mir b/doc/INSTALL.mir
index f359b5e4..190efc9a 100755
--- a/doc/INSTALL.mir
+++ b/doc/INSTALL.mir
@@ -245,6 +245,9 @@ will allow searching based off of media type.  (This is possible
 because the standard templates will include META keywords like
 hasAudio, hasVideo, etc.)  
 
+UPGRADING
+
+see the UPGRADING.mir file.
 
 TROUBLESHOOTING
 
diff --git a/doc/UPGRADING.mir b/doc/UPGRADING.mir
new file mode 100755
index 00000000..92d3d832
--- /dev/null
+++ b/doc/UPGRADING.mir
@@ -0,0 +1,23 @@
+MIR UPGRADING HOWTO
+----------------------------------------------------------------
+
+Due to weaknesses of the current Mir configuration system, many folks get
+bitten after doing an update of their cvs tree. Suddenly Mir starts throwing
+weird exceptions, etc.. The cause is usually a new config option in the
+source/config.properties-dist that is missing from your
+source/config.properties file (the one that is actually used).
+
+a good way to check for this is to do the following (in the mir/ directory):
+
+cd source
+diff -u config.properties config.properties-dist
+
+for this unfamiliar with the diff(1) program, you'll see a bunch of lines, some
+starting with a "+" or "-". Look for a bunch of consecutive "+" symbols not
+immeadiately followed by a "-". that usually is a new config option that you
+should copy/paste (without the "+"'s of course) over to your existing
+config.properties file and modify if necessary.
+
+----------------------------------------------------------------
+
+2002 - the Mir coders