Log Message:
-----------
slon.env now references the environment variable SLONYENV as an
alternative source for information on cluster configuration, thus
allowing multiple clusters to use the same set of Slony setup scripts.

Modified Files:
--------------
    slony1-engine/tools/altperl:
        slon.env (r1.1 -> r1.2)
        README (r1.2 -> r1.3)

-------------- next part --------------
Index: slon.env
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/tools/altperl/slon.env,v
retrieving revision 1.1
retrieving revision 1.2
diff -Ltools/altperl/slon.env -Ltools/altperl/slon.env -u -w -r1.1 -r1.2
--- tools/altperl/slon.env
+++ tools/altperl/slon.env
@@ -2,6 +2,10 @@
 # Author: Christopher Browne
 # Copyright 2004 Afilias Canada
 
+if ($ENV{"SLONYENV"}) {
+  require $ENV{"SLONYENV"};
+} else {
+  # Define environment locally...
 $SETNAME=flex2test;
 $LOGDIR='/opt/logs/slon';
 $SLON_BIN_PATH='/opt/OXRS/dbs/pgsql74/bin';
@@ -124,3 +128,4 @@
 	    "dns_update_id_seq"
 	   );
 
+}
Index: README
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/tools/altperl/README,v
retrieving revision 1.2
retrieving revision 1.3
diff -Ltools/altperl/README -Ltools/altperl/README -u -w -r1.2 -r1.3
--- tools/altperl/README
+++ tools/altperl/README
@@ -26,14 +26,22 @@
 Alas, this means that the values are "hardcoded" as far as the tools
 are concerned.
 
-The natural extension to be added to this to make it more flexible
-would be for slon.env to look at an environment variable to see what
-file these lists are found in.  That way, you could do something like:
+To make this more flexible, slon.env looks at the environment variable
+SLONYENV as an alternative source for this configuration.  
+
+That way, you may do something like:
 
    for i in `seq 10`; do
       SLONYENV="./set$i.config" ./init_cluster.pl
    done
 
+- Such an "alternative slon.env" might import Pg, and do queries
+against a database to be replicated in order to populate the sets of
+tables and such.
+
+- The "alternative slon.env" might search some sort of 'registry' for
+the set of nodes to be replicated.
+
 Steps to start up replication
 -------------------------------