i second that motion, strongly in favor of dbconfig-common. the typical way to do things as described in the calidav wiki works fine when followed precisely, but due to the "local all all trust" step it is inacceptable for setup on production servers while they are in use. (i'm not sure the setup described there is safe for systems with local users at all.)
especially for users who don't know a thing about postgres, that would help a lot (and might even avoid inseucre setups by providing a default that works)
signature.asc
Description: Digital signature
