The freeswitch-all package provides libfreeswitch1, so any
shlibs-generated dependency should be for libfreeswitch1 rather than
freeswitch-all.
Because dh_shlibdeps / dpkg-shlibdeps searches for shlibs files in
debian/*/DEBIAN/ it was sometimes using freeswitch-all rather than
libfreeswitch1 to satisfy dependencies for freeswitch.so.1.
FS-6029 --resolve
The various sounds and music have their own source packages now as
they have their own conventions and version numbers which fortunately
update less frequently than FreeSWITCH itself.
Debian expects all copyright information to be in one place, so we
copy the license details to debian/copyright and remove the COPYING
files when we install components.
We believe there may be a race condition in bootstrap.sh when run with
-j. We know that running it without -j should be at least
deterministic (whether or not correct), so we'll go with that in
anticipation of releasing v1.2.
We now break out each module and component of FreeSWITCH into a
separate individually-installable package. For each package with
executables or modules, we also build a package that includes the
stripped debugging symbols so that users can be helpful when they
discover bugs in FreeSWITCH.
As of this commit, we successfully build 263 distinct binary packages
starting from a clean minimal image on both Debian Sid and Debian
Squeeze.
To keep this manageable, we include a program that generates the
various Debian packaging files from a consolidated description of the
modules and their metadata. The program can even generate this
configuration file by walking the FreeSWITCH source tree.
To provide a smooth user experience, we provide meta-packages that
install sensible sets of modules and other components.
All files are installed into the traditional and customary Linux
directories that you would expect in accordance with the Filesystem
Hierarchy Standard (FHS).
This commit also adds support for running FreeSWITCH as a forked
systemd service in Debian.
For more information about the technical details of the source
packaging, how to build the binary packages from source, and how you
can contribute, please read debian/README.source.
To learn about how this packaging affects you as a user and how to use
the finished Debian packages, read debian/README.Debian.
Signed-off-by: Travis Cross <tc@traviscross.com>
Peter Wu