[coldsync-hackers] Snapshot: 1.4.3

[Andrew Arensburger <arensb@ooblick.com>]

	I've just uploaded another snapshot, version 1.4.3 this time.
	The big change is that the built-in generic conduit is just
another Sync conduit: you can run it by specifying
	conduit sync {
		type: crea/type;
		path: [generic];
	}
in the .coldsyncrc (yes, with the brackets). This allows you to specify
whether, how, and when the generic conduit will be run with respec to
other conduits.

	The initial configuration now appends a conduit block at the
beginning, equivalent to:

	conduit sync {
		type: */*;
		path: [generic];
		default;
	}

This (mostly) preserves existing behavior: if you don't specify a Sync
conduit for a database, it will be backed up or synced, as appropriate.
	The main thing that this breaks is that if you currently _do_ have
a Sync conduit specified for a database, then the generic conduit will not
be run; you'll have to add another conduit block for that manually.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com			views of ooblick.com
       If that makes any sense to you, you have a big problem.


--
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.