<div class="gmail_extra"><div class="gmail_quote">On Wed, Nov 14, 2012 at 12:54 PM, Paul Belanger <span dir="ltr"><<a href="mailto:paul.belanger@polybeacon.com" target="_blank">paul.belanger@polybeacon.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">On 12-11-14 12:02 PM, Daniel Pocock wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Following up from the SIP stack discussion, I think it may be useful to<br>
have a separate thread to get comments from people about the<br>
relationship of Asterisk with distributions.<br></blockquote></div></div></blockquote><div><br>I'm the Asterisk packager for Fedora. I do the packaging work on my free time, I do not work for Digium or RedHat and my current employer does not pay me to do the packaging either, although having Asterisk packaged for Fedora certainly comes in handy at work.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- release cycles/cut off dates (e.g. Debian was `frozen' a few months<br>
ago, no new Asterisk packages will be allowed until the next `stable'<br>
release in 2 years, although updated packages can be distributed in<br>
backports)<br></blockquote></div></div></blockquote><div><br>Fedora doesn't really work that way. New packages can be distributed, as long as it's primarily a bug-fix release. Major version upgrades that introduce new features and incompatibilities should only be introduced in a new version of Fedora.<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- maintenance cycles (e.g. Debian releases need 3 years of security<br>
updates, RHEL needs 7, which is a long time for VoIP)<br></blockquote></div></div></blockquote><div><br>Yes, see below as support for Asterisk 1.8 will end before support for RHEL 6 does.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- interaction with the packaging process (e.g. more people joining as<br>
Debian maintainer, which is a stepping-stone to becoming a full Debian<br>
Developer)<br>
<br>
- interaction with the support process (e.g. using Debian's bug tracker)<br></blockquote></div></div></blockquote><div><br>I handle it by telling people that report any non-packaging bugs in RedHat's Bugzilla to report the bugs themselves to Digium's bug tracker. I don't have the time, equipment, or knowledge of the Asterisk codebase to do any debugging of the problem on my own, and I won't act as an intermediary between Digium's bug tracker and RedHat's bug tracker.<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- addressing all of the above issues for dependencies, e.g. if using<br>
libsrtp or resiprocate, how to make sure that distributions are all<br>
carrying the version required by Asterisk?<br></blockquote></div></div></blockquote><div><br>I handle it by being the packager for a number of the dependencies that Asterisk requires, at least the unique ones like libpri or spandsp.<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
This last issue (dependencies) is sometimes perceived as a major pain in<br>
itself - but if it is planned from the beginning and co-ordinated with<br>
other projects, it can be managed and it can work favorably.<br>
<br>
At the end of the day, distributions bring a lot of users, and if<br>
everything is planned well, then users don't have to ask questions about<br>
dependencies or how to install. This saves valuable support time.<br>
<br>
I've worked with companies that just do telecoms and they don't mind<br>
having bespoke servers for their apps, nor do they object to paying<br>
fees for a freelance developer to fine tune everything. However, as<br>
more and more IT managers want VoIP, they don't want to spend time<br>
building anything from source, they want the convenience of installing<br>
with apt-get or yum, just like they do with Apache or Postfix or Mysql.<br>
<br>
Having some clarity about these relationships may give insights about<br>
the priorities for the SIP stack question.<br></blockquote></div></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
<div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>
So, lets us the following example right now with Asterisk 11, since we are already embedding pjproject in Asterisk and from what I understand it is a core dependency.<br></blockquote><div><br>Fedora 18 will be released with Asterisk 11. I knew about pjproject but I basically ignored it (except for figuring out how to get it to build) as licensing gives me headaches. I posted a message to fedora-devel last month about my plans for maintaining Asterisk in Fedora/EPEL:<br>
<br><a href="http://lists.fedoraproject.org/pipermail/devel/2012-October/172286.html">http://lists.fedoraproject.org/pipermail/devel/2012-October/172286.html</a><br><br>The main takeaway is that EPEL6 (for RHEL6 and derivatives) will be supported for long past the time that Digium stops supporting Asterisk 1.8. Since EPEL is supposed to be all "enterprisey" and not do upgrades that introduce new features and deprecate old ones that's a problem because I'm not going to be spending my personal time to backport security patches on my own once Digium stops supporting Asterisk 1.8.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I haven't talked with debian-voip yet, but I'm sure there is already some concern with packaging Asterisk 11 for Debian. IIRC, nothing has been started yet and I suspect having pjproject embedded into Asterisk is going to be a hot topic.<br>
<br>
Would you expect distributions to remove the dependency on pjproject? Or worst, not package Asterisk because of policy?<br>
<br>
It would also be good to hear what Fedora's plans are too.<span class=""><font color="#888888"></font></span></blockquote><div> </div></div>See the above link...<br clear="all"><br>-- <br>Jeff Ollie<br><br><br>
</div>