Oh damn that's a good point - well spotted<div><br></div><div>Cal<br><div><br><div class="gmail_quote">On Tue, Mar 12, 2013 at 5:33 PM, Steven Ayre <span dir="ltr"><<a href="mailto:steveayre@gmail.com" target="_blank">steveayre@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">You may not have noticed there are meta packages. If you install<br>
</span><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">freeswitch-meta-all you'll get everything pulled in.</span></blockquote><div><font color="#222222" face="arial, sans-serif"><br>
</font></div></div><div><font color="#222222" face="arial, sans-serif">You can also build your own meta package that depends on all the packages required by your application. Then it's simply a case of:</font></div><div>
<font color="#222222" face="arial, sans-serif">$ sudo apt-get install freeswitch-meta-companyname</font></div>
<div><font color="#222222" face="arial, sans-serif"><br></font></div><div><font color="#222222" face="arial, sans-serif">-Steve</font></div><div class="HOEnZb"><div class="h5"><div><font color="#222222" face="arial, sans-serif"><br>
</font></div><div><font color="#222222" face="arial, sans-serif"><br>
</font><br><div class="gmail_quote">On 12 March 2013 15:28, Travis Cross <span dir="ltr"><<a href="mailto:tc@travislists.com" target="_blank">tc@travislists.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Cal,<br>
<br>
It looks like others did rather well at answering these, so I'll just<br>
fill in some points.<br>
<div><br>
On 2013-03-12 12:44, Cal Leeming [Simplicity Media Ltd] wrote:<br>
> So today I went to go and create a Debian package for FreeSWITCH<br>
> using the existing packaging structure;<br>
><br>
> <a href="https://github.com/traviscross/freeswitch/blob/master/debian/" target="_blank">https://github.com/traviscross/freeswitch/blob/master/debian/</a><br>
> <a href="http://wiki.freeswitch.org/wiki/Debian_packages_buildscript" target="_blank">http://wiki.freeswitch.org/wiki/Debian_packages_buildscript</a><br>
><br>
> The first problem is that neither the helper or the debian/ dir have<br>
> been configured for compatibility with pbuilder, which makes it<br>
> untidy/non-sane to place this onto an automated production build<br>
> system (it also impacts security slightly due to untrusted external<br>
> code being ran outside of a chroot - but that's possibly an entirely<br>
> different debate).<br>
<br>
</div>It works fine with pbuilder and cowbuilder. If you take a look at the<br>
util.sh script, which is what I use to do the builds, you'll see I use<br>
cowbuilder there as well.<br>
<div><br>
> The second problem is that the build resulted in nearly 100<br>
> different *.deb files This also poses somewhat of an annoyance in<br>
> automated deployment environments, for example saltstack, where the<br>
> configuration would have to list each individual FreeSWITCH<br>
> module.<br>
<br>
</div>You may not have noticed there are meta packages. If you install<br>
freeswitch-meta-all you'll get everything pulled in.<br>
<div><br>
> It also feels very untidy. I understand that certain packages (such<br>
> as libfreeswitch, libfreeswitch-dev, freeswitch-server etc) should<br>
> be separated. But having a package for each module, the only use I<br>
> could think of for this, would be if the Debian package compiles<br>
> absolutely every module possible, and is then linked dynamically,<br>
> rather than compiled static. This means enabling/disabling modules<br>
> would be a matter of simply adding/removing a package.<br>
<br>
</div>Yes, that's exactly how it works.<br>
<div><br>
> However I'm not entirely convinced if this is what it is<br>
> doing.. when compiling absolutely every package possible, FreeSWITCH<br>
> will usually fail to compile, due to collision etc.<br>
><br>
> So I have a couple of questions;<br>
><br>
> 1) Why are the modules separated into individual files?<br>
><br>
> 2) Are there any reasons to not be using pbuilder?<br>
><br>
> I have also CC'd Travis Cross who appears to a major contributor on<br>
> the Debian packaging code.<br>
<br>
</div>Please also be sure to read debian/README.{Debian,source}.<br>
<br>
Best,<br>
<br>
--<br>
Travis Cross<br>
<div><div><br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">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" target="_blank">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>
</div></div></blockquote></div><br></div>
</div></div><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></div></div>