I've been using that build script in chroots for the matrix of [i368,amd64] x [sid,squeeze,wheezy]<div><br></div><div>The answer to question 1 is it builds all modules, including ones you don't necessarily want, so you can install just the modules you want on your production machines to save disk space, etc.<br>
<br><div class="gmail_quote">On 12 March 2013 12:44, Cal Leeming [Simplicity Media Ltd] <span dir="ltr"><<a href="mailto:cal.leeming@simplicitymedialtd.co.uk" target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey,<div><br></div><div>So today I went to go and create a Debian package for FreeSWITCH using the existing packaging structure;</div>
<div><br></div><div><a href="https://github.com/traviscross/freeswitch/blob/master/debian/" target="_blank">https://github.com/traviscross/freeswitch/blob/master/debian/</a></div>
<div><a href="http://wiki.freeswitch.org/wiki/Debian_packages_buildscript" target="_blank">http://wiki.freeswitch.org/wiki/Debian_packages_buildscript</a></div><div><br></div><div>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).</div>
<div><br></div><div>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.</div>
<div><br></div><div>So I have a couple of questions;</div><div><br></div><div>1) Why are the modules separated into individual files? </div><div><br></div><div>2) Are there any reasons to not be using pbuilder?</div><div>
<br></div><div>I have also CC'd Travis Cross who appears to a major contributor on the Debian packaging code.</div><div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Cal</div>
</font></span><br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><b>Andrew Cassidy BSc (Hons) MBCS SSCA</b><div>Managing Director<div><div><img src="http://c1170247.r47.cf3.rackcdn.com/emailsig.png"><br></div><div><br><div>
<b style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif"><a href="mailto:info@cassidywebservices.co.uk" style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif" target="_blank">T</a> </b>03300 100 960
<b style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif"><a href="mailto:info@cassidywebservices.co.uk" style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif" target="_blank">F</a> </b>03300 100 961</div>
<div><b style="text-decoration:none;font-family:sans-serif"><a href="mailto:info@cassidywebservices.co.uk" style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif" target="_blank">E</a> </b><a href="mailto:andrew@cassidywebservices.co.uk" target="_blank">andrew@cassidywebservices.co.uk</a></div>
<div><b style="text-decoration:none;font-family:sans-serif"><a href="mailto:info@cassidywebservices.co.uk" style="color:rgb(51,135,171);text-decoration:none;font-family:sans-serif" target="_blank">W</a> </b><a href="http://www.cassidywebservices.co.uk" target="_blank">www.cassidywebservices.co.uk</a></div>
</div></div></div>
</div>