<div dir="ltr">Thanks Daniel for response<br>Sure packaging rules must be same for all dists.<br>Could you make same comment at <a href="https://github.com/kamailio/kamailio/issues/1862">https://github.com/kamailio/kamailio/issues/1862</a><br><br>This will allow track this request</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">чт, 21 февр. 2019 г. в 12:31, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hello,<br>
</p></div><div text="#000000" bgcolor="#FFFFFF">
<div class="m_-2611731843244548946moz-cite-prefix">On 21.02.19 07:39, Sergey Safarov
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Current kamailio package (checked via RPM) is contains lot
of modules. Some of this is not important to include in every
kamailio installation. May be create own packages for this
modules and other in next 5.3 branch?</div>
<div>Modules examples:</div>
<div><br>
</div>
<div><font face="monospace">benchmark.so<br>
</font></div>
<div><font face="monospace">db_cluster.so</font></div>
<div><font face="monospace">db_text.so</font></div>
<div><font face="monospace">rtpengine.so</font></div>
<div><font face="monospace">rtpproxy.so</font></div>
<div><font face="monospace">sipcapture.so</font></div>
<div><font face="monospace">siptrace.so</font></div>
<div><font face="monospace">sipt.so</font></div>
<div><font face="monospace">sms.so</font></div>
<div><font face="monospace">smsops.so</font></div>
<div><font face="monospace">ss7ops.so</font></div>
<div><br>
</div>
<div><a href="https://github.com/kamailio/kamailio/issues/1862" target="_blank">https://github.com/kamailio/kamailio/issues/1862</a><br>
</div>
<div><br>
</div>
</div>
</blockquote>
</div><div text="#000000" bgcolor="#FFFFFF"><p>use of such modules is a matter of deployment type and for
example, for residential services, rtpengine or rtpproxy are like
a must. I also use often benchmark module to track execution of
some operations (like http queries). Also, siptrace is rather
common in what I deal with.<br>
</p>
<p>IMO, it is hard to make a selection on usage or personal
preferences. The rule was that was has same dependencies as core,
they should be packaged together.</p>
<p>Actually there was a discussion to add more to the main package,
from those with additional dependencies, but very used (like tls,
...) -- it might be on issue tracker as well.</p>
<p>Then, Victor Seva mentioned at some point in time that in debian
is better to keep modules groupped as many as possible, because
introducing a new package in the official distro requires a
complex process of review for license, etc...</p>
<p>Overall, if there is a decision to regroup some modules in
different packages, I would like to follow the same for both debs
and rpms, otherwise installation guidelines can end up to be
different and can become confusing.</p>
<p>Cheers,<br>
Daniel<br>
</p></div><div text="#000000" bgcolor="#FFFFFF">
<pre class="m_-2611731843244548946moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="m_-2611731843244548946moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a>
<a class="m_-2611731843244548946moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a class="m_-2611731843244548946moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
Kamailio World Conference - May 6-8, 2019 -- <a class="m_-2611731843244548946moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a>
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- <a class="m_-2611731843244548946moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a></pre>
</div></blockquote></div>