Clean up the libpq autodection and make sure it functionswith both pg_config and pkg-config.

if you are installing into a non-FHS standard location such as what happens with RPMs from the Postgres yum repo, you will need to make sure pkg-config can fild the libpq.pc file.
example: export PKG_CONFIG_PATH=/usr/pgsql-9.3/lib/pkgconfig

you may also want to make sure your path can find pg_config
example: export PATH=/usr/pgsql-9.3/bin:$PATH

also merge bkw's typo aliases

Conflicts:
	support-d/.bashrc

./debian/util.sh build-all will do a number of builds in sequence or
parallel.  We now track if any of those builds fail to return a
.changes file and exit non-zero.

FS-6230 --resolve There was no NAT detection enabled on the calls, this patch will activate it explicitly when used with force-rport to avoid a similar problem with other users

Conflicts:
	src/mod/endpoints/mod_sofia/sofia.c

regression from 8f82979d using wrong values to calculate buffer size

Conflicts:
	src/mod/applications/mod_conference/mod_conference.c

Conflicts:
	src/mod/applications/mod_conference/mod_conference.c

This amends commit b9a85831.

had to fix an issue that broke centos 5

The rebuild is needed for commit cd6154b4.

If this is set to true (default false) we assume the storage-dir is
shared, organized by realm/domain, with uses other than voicemail, so
we adopt a directory structure of:

  <storage_dir>/<realm>/voicemail/<id>

This replaces the semantics of the storage-dir parameter without the
deprecation notice.  The behavior of storage-dir never should have
been deprecated, though it was probably correct to deprecate the name
itself.

Rather than having both vm-storage-dir and vm-domain-storage-dir it
might be nice if the config system could just notice at what level it
was defined and do the right thing.  Indeed, this is why I'd left
things as-is for so long.

But as Master Foo famously said, "which one will reach the other side
of the river: the one who dreams of a raft, or the one that hitchhikes
to the next bridge?"

FS-5329