freeswitch/debian
2012-05-12 18:23:33 +00:00
..
source
.gitignore debian: remove remnants of slimplayer as we're now packaging this under contrib 2012-05-11 02:03:58 +00:00
bootstrap.sh debian: use libjpeg62-dev rather than libjpeg8-dev 2012-05-12 18:23:32 +00:00
changelog
compat
control-modules debian: add build-depends and suggests for mod_ladspa 2012-05-12 18:23:33 +00:00
copyright
docs
freeswitch-doc.docs
freeswitch-doc.install
freeswitch-mod-pocketsphinx.install.tmpl
freeswitch-systemd.freeswitch.service
freeswitch-systemd.install
freeswitch-sysvinit.freeswitch.default
freeswitch-sysvinit.freeswitch.init
freeswitch.install debian: separate out libfreeswitch1 2012-05-09 23:15:02 +00:00
freeswitch.postinst debian: whitespace 2012-05-06 22:46:36 +00:00
freeswitch.postrm debian: whitespace 2012-05-06 22:46:36 +00:00
freeswitch.preinst debian: whitespace 2012-05-06 22:46:36 +00:00
freeswitch.prerm debian: massage the prerm script to pass lintian 2012-05-07 16:17:11 +00:00
gbp.conf
libfreeswitch1.install debian: separate out libfreeswitch1 2012-05-09 23:15:02 +00:00
libfreeswitch-dev.install debian: don't distribute .la file with libfreeswitch-dev 2012-05-09 23:15:03 +00:00
README.Debian
README.source
rules debian: attribution 2012-05-11 00:35:17 +00:00
util.sh debian: mirror dpkg-source parameter choice 2012-05-11 06:23:18 +00:00

FreeSWITCH for Debian
--------------

You may be reading this because you're wondering where all the files
are in debian/, such as control.

Because FreeSWITCH has so many modules it was necessary to create a
system to autogenerate the majority of the packaging.  This in done
mostly in the file debian/bootstrap.sh.  This bootstrap needs to run
before any other step of the packaging, though we do try to
autogenerate it when possible.

The build dependencies, runtime dependencies, and other details about
modules can be configured in the debian/control-modules file.  Even
though this file looks a bit like a debian control file and has a
similar format, we are parsing this file ourselves so the format is a
bit more restricted.

debian/control-modules currently supports the following fields:

  # lines that begin with the hash character are comments
  #
  # every block must start with a Module field
  Module: <category>/<module_name>
  Description: <short description>
   <long description> # empty lines with "."s are not yet supported
  Build-Depends: <build deps for this module>
  Depends: <runtime deps for this module>
  Recommends: <recommended packages>
  Suggests: <suggested packages>
  Distro-Conflicts: <distributions on which this module should not be built> # not yet implemented

During bootstrap we build a file control-modules.gen.  If the
control-modules file is properly formatted, this generated file should
be identical.  This is a sanity check mechanism for our parsing, as
well as a way to automatically reorganize the file.

If the file debian/modules.conf is present, we read that file and only
build and package the files listed there.  Otherwise, we build every
module except the ones that either should not be packaged, or for
which we don't yet have good packaging.

The format of debian/modules.conf is:

  ## comments should start with two hash characters
  <category>/<module_name>

To build this package, I recommend running the following from the root
directory of your FS git working tree:

  mkdir ../sounds
  export FS_SOUNDS_DIR=$(pwd)/../sounds
  git clean -fdx && git reset --hard HEAD
  (cd debian && ./bootstrap.sh)
  schedtool -B -e git-buildpackage --git-verbose -us -uc

 -- Travis Cross <tc@traviscross.com>, Sat,  5 May 2012 23:32:53 +0000