Previously we were creating freeswitch-music, freeswitch-sounds,
freeswitch-sounds-en, and freeswitch-sounds-en-us metapackages and
also providing those names as virtual packages from the
freeswitch-{sounds,music} source packages. This is unnecessarily
confusing and meant that freeswitch-all wasn't depending on any sounds
in actuality as it was also providing freeswitch-sounds.
That is to say, declare all appropriate Provides/Conflicts/Replaces
for freeswitch-all and freeswitch-all-dbg by enumerating the binary
packages that we're going to produce during the build.
Conflicts is more appropriate than Breaks here as both packages will
continue to provide the same files on an ongoing basis and we would
like to force the removal of the other package.
At this point we never want someone running a module against a
different version of FS than the module was built for. It's also
conceivable that you could want to use the modules with libfreeswitch1
even if you weren't running FS itself.
We now build unimrcp, portaudio, portaudio-stream, skypopen, b64, and
dahdi-codec, so they should be included in meta-all. Also refactor a
bit so we install all lang and mod_say packages as well.
Languages are installed at /usr/share/freeswitch/lang so that they can
be referred to by the user's configuration in /etc/freeswitch. As a
Debian package user isn't going to have access to `make vm-sync` these
files need to be readily available somewhere.
libopenh323-dev is in squeeze and sid, but it doesn't look like it's
going to make it into wheezy at this point.
H323Plus claims to be a drop-in replacement, but this should probably
be tested thoroughly.
Note that mod_h323 is still in the avoid_mods list pending testing to
verify that it builds cleanly on each target.
Thanks-to: Steven Ayre <steveayre@gmail.com>
FS-4567 --resolve
It's broken too many of my recent builds. We can add it back in when
things stabilize or perhaps after we get it to swig with a recent
version of swig that we can make part of the clean bootstrap/build
process.
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.
We're not including the source code or build tools for the version of
the player we're distributing, so it fails The Debian Free Software
Guidelines (DFSG).
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>
Travis Cross