[Freeswitch-users] Debian packaging - some questions

[Cal Leeming [Simplicity Media Ltd]]

Hey,

So today I went to go and create a Debian package for FreeSWITCH using the
existing packaging structure;

https://github.com/traviscross/freeswitch/blob/master/debian/
http://wiki.freeswitch.org/wiki/Debian_packages_buildscript

The first problem is that neither the helper or the debian/ dir have been
configured for compatibility with pbuilder, which makes it untidy/non-sane
to place this onto an automated production build system (it also impacts
security slightly due to untrusted external code being ran outside of a
chroot - but that's possibly an entirely different debate).

The second problem is that the build resulted in nearly 100 different *.deb
files This also poses somewhat of an annoyance in automated deployment
environments, for example saltstack, where the configuration would have to
list each individual FreeSWITCH module. It also feels very untidy. I
understand that certain packages (such as libfreeswitch, libfreeswitch-dev,
freeswitch-server etc) should be separated. But having a package for each
module, the only use I could think of for this, would be if the Debian
package compiles absolutely every module possible, and is then linked
dynamically, rather than compiled static. This means enabling/disabling
modules would be a matter of simply adding/removing a package. However I'm
not entirely convinced if this is what it is doing.. when compiling
absolutely every package possible, FreeSWITCH will usually fail to compile,
due to collision etc.

So I have a couple of questions;

1) Why are the modules separated into individual files?

2) Are there any reasons to not be using pbuilder?

I have also CC'd Travis Cross who appears to a major contributor on the
Debian packaging code.

Thanks

Cal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130312/e2f4bda2/attachment.html